From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
"Cureington, Tony" <tony.cureington@hp.com>,
Pascal Brisset <pascal.brisset-ml@wanadoo.fr>,
bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: PATCH Re: [Bonding-devel] Re: Bonding driver unreliable under high CPUload
Date: Wed, 18 Sep 2002 21:03:48 -0400 [thread overview]
Message-ID: <3D892274.4070600@mandrakesoft.com> (raw)
In-Reply-To: OF516AEB0B.459BB3DC-ON88256C39.0004B863@boulder.ibm.com
Jay Vosburgh wrote:
>
> No, it doesn't. This is a mere band aid until somebody can get time
> to do it right. It's "less bad."
Oh, well, in that case, patch approved :)
I'll apply it, unless you prefer to send it through DaveM or somebody else.
Jeff
next prev parent reply other threads:[~2002-09-19 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 0:56 PATCH Re: [Bonding-devel] Re: Bonding driver unreliable under high CPUload Jay Vosburgh
2002-09-19 1:03 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 0:23 Jay Vosburgh
2002-09-19 0:48 ` Jeff Garzik
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=3D892274.4070600@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=akpm@digeo.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=pascal.brisset-ml@wanadoo.fr \
--cc=tony.cureington@hp.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).