mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: driver@megahappy.net (Bryan Whitehead)
To: ctindel@users.sourceforge.net
Cc: bonding-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.2] drivers/net/bonding/bond_alb.c
Date: Wed,  4 Feb 2004 15:33:56 -0800 (PST)	[thread overview]
Message-ID: <20040204233356.485BBFA5F1@mrhankey.megahappy.net> (raw)

Building with gcc 3.3.2 on gentoo linux on Athlon x86 system I get
a warning:
  CC [M]  drivers/net/bonding/bond_alb.o
drivers/net/bonding/bond_alb.c: In function `bond_alb_xmit':
drivers/net/bonding/bond_alb.c:1340: warning: comparison is always true due to limited range of data type                                                                                                         
This is due to using __constant_htons for endian issues. This is a byte so there
is no point in using __constant_htons in the first place. Unless I'm mistaken using
__constant_htons makes this statment always true as the compiler states.
 
if ipx_type = IPX_TYPE_NCP then the intended logic will not happen?

--- linux-2.6.2/drivers/net/bonding/bond_alb.c.orig     2004-02-04 15:08:04.228336168 -0800
+++ linux-2.6.2/drivers/net/bonding/bond_alb.c  2004-02-04 15:26:03.769221008 -0800
@@ -1336,8 +1336,7 @@ bond_alb_xmit(struct sk_buff *skb, struc
                        break;
                }
  
-               if (ipx_hdr(skb)->ipx_type !=
-                   __constant_htons(IPX_TYPE_NCP)) {
+               if (ipx_hdr(skb)->ipx_type != IPX_TYPE_NCP) {
                        /* The only protocol worth balancing in
                         * this family since it has an "ARP" like
                         * mechanism


--
Bryan Whitehead
Email:driver@megahappy.net
WorkE:driver@jpl.nasa.gov

             reply	other threads:[~2004-02-04 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 23:33 Bryan Whitehead [this message]
2004-02-05  6:50 Bryan Whitehead
2004-02-05  6:55 ` Bryan Whitehead

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=20040204233356.485BBFA5F1@mrhankey.megahappy.net \
    --to=driver@megahappy.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=ctindel@users.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®