public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-patches@ecos.sourceware.org
Subject: [Issue 1001170] Correct Endianness of DHCP "Seconds Elapsed" field
Date: Wed, 09 Mar 2011 23:59:00 -0000	[thread overview]
Message-ID: <20110309235948.E801D2F78008@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001170-104@http.bugzilla.ecoscentric.com/>

Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1001170

--- Comment #2 from Jay Foster <jay@systech.com> 2011-03-09 23:59:47 GMT ---
It also appears in bootp_support.c: show_bootp().

Depending on the implementation of htons(), cyg_current_time() may end 
up getting called twice.  Might be better to put the result of 
cyg_current_time() / 100 in a temporary variable and perform htons() on 
that.

Jay

On 3/9/2011 10:26 AM, bugzilla-daemon@bugs.ecos.sourceware.org wrote:
> Please do not reply to this email. Use the web interface provided at:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001170
>
> --- Comment #1 from Sergei Gavrikov<sergei.gavrikov@gmail.com>  2011-03-09 18:26:22 GMT ---
> Created an attachment (id=1167)
 --> (https://bugzilla.ecoscentric.com/attachment.cgi?id=1167)
>   -->  (http://bugs.ecos.sourceware.org/attachment.cgi?id=1167)
> Fixed byte order for bp_secs
>
> diffstat /tmp/dhcp_prot.diff
>   ChangeLog       |    5 +++++
>   src/dhcp_prot.c |    2 +-
>   2 files changed, 6 insertions(+), 1 deletion(-)
>
> Grep shows 1 actual place. Hope that's it.
>

-- 
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the issue.

           reply	other threads:[~2011-03-09 23:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-1001170-104@http.bugzilla.ecoscentric.com/>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110309235948.E801D2F78008@mail.ecoscentric.com \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=ecos-patches@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).