netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason Lunz" <lunz@reflexsecurity.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: netdev@oss.sgi.com
Subject: Re: e1000 typo?
Date: Wed, 30 Jul 2003 14:29:06 -0400	[thread overview]
Message-ID: <20030730182906.GA14121@reflexsecurity.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102229242@orsmsx402.jf.intel.com>

On Wed, Jul 30, 2003 at 11:24AM -0700, Feldman, Scott wrote:
> It's intentional because && stops evaluating if left op is false which
> means we would leave Tx cleanup work when there was no Rx work.  

ah. subtle yet obvious. :P

-- 
Jason Lunz			Reflex Security
lunz@reflexsecurity.com		http://www.reflexsecurity.com/

  reply	other threads:[~2003-07-30 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 18:24 e1000 typo? Feldman, Scott
2003-07-30 18:29 ` Jason Lunz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30 17:21 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=20030730182906.GA14121@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 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 NNTP newsgroup(s).