From: Harvey Harrison <harvey.harrison@gmail.com>
To: Eilon Greenstein <eilong@broadcom.com>
Cc: linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 8/9] bnx2x: further annotations
Date: Thu, 22 Jan 2009 10:17:04 -0800 [thread overview]
Message-ID: <1232648224.9701.53.camel@brick> (raw)
In-Reply-To: <1232646594.29087.88.camel@lb-tlvb-eliezer>
On Thu, 2009-01-22 at 19:49 +0200, Eilon Greenstein wrote:
> On Tue, 2009-01-20 at 21:50 -0800, Harvey Harrison wrote:
> > No functional annotations, just documenting the status quo.
> >
> > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
>
> [...]
>
> > @@ -9699,11 +9699,11 @@ static int bnx2x_start_xmit(struct sk_buff *skb, struct net_device *dev)
> > bd_prod, ++nbd);
> >
> > pbd->lso_mss = cpu_to_le16(skb_shinfo(skb)->gso_size);
> > - pbd->tcp_send_seq = swab32(tcp_hdr(skb)->seq);
> > + pbd->tcp_send_seq = cpu_to_le32(be32_to_cpu(tcp_hdr(skb)->seq));
>
> Hmmm.... That looks worse to me. Do we really need to replace swab with
> cpu_to_le on top of be_to_cpu?
Agreed that it is ugly, in a future patch I was thinking of changing tcp_send_seq
to just be treated as a be-value throughout the driver, or at least a cpu-endian.
These patches are more about documenting the status quo than making functional
changes like that, so I went with the somewhat ugly annotation for now. Once
the endian noise has been reduced, it will be a lot easier to make changes
without introducing bugs.
Harvey
prev parent reply other threads:[~2009-01-22 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 5:50 [PATCH 8/9] bnx2x: further annotations Harvey Harrison
2009-01-22 17:49 ` Eilon Greenstein
2009-01-22 18:17 ` Harvey Harrison [this message]
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=1232648224.9701.53.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.