From: "Jason Lunz" <lunz@reflexsecurity.com>
To: scott.feldman@intel.com
Cc: netdev@oss.sgi.com
Subject: e1000 typo?
Date: Wed, 30 Jul 2003 13:21:10 -0400 [thread overview]
Message-ID: <20030730172110.GA13929@reflexsecurity.com> (raw)
The diff between the 5.1.11 and the newest e1000 drivers has this hunk:
@@ -1999,7 +1996,7 @@
}
#else
for(i = 0; i < E1000_MAX_INTR; i++)
- if(!e1000_clean_rx_irq(adapter) &&
+ if(!e1000_clean_rx_irq(adapter) &
!e1000_clean_tx_irq(adapter))
break;
#endif
is that intentional? I don't think it changes the code behavior, but it
doesn't look right.
--
Jason Lunz Reflex Security
lunz@reflexsecurity.com http://www.reflexsecurity.com/
next reply other threads:[~2003-07-30 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 17:21 Jason Lunz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 18:24 e1000 typo? Feldman, Scott
2003-07-30 18:29 ` Jason Lunz
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=20030730172110.GA13929@reflexsecurity.com \
--to=lunz@reflexsecurity.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
/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.