From: Jeff Garzik <jgarzik@pobox.com>
To: Shmulik Hen <hshmulik@intel.com>
Cc: Bonding Developement list <bonding-devel@lists.sourceforge.net>,
Bonding Announce list <bonding-announce@lists.sourceforge.net>,
Linux Net Mailing list <linux-net@vger.kernel.org>,
Linux Kernel Mailing list <linux-kernel@vger.kernel.org>,
Oss SGI Netdev list <netdev@oss.sgi.com>
Subject: Re: [patch] (0/8) Adding 802.3ad support to bonding
Date: Thu, 20 Mar 2003 11:56:18 -0500 [thread overview]
Message-ID: <20030320165618.GB8256@gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303201553540.10351-100000@jrslxjul4.npdj.intel.com>
I (and many others) will be going over these patches. I also see that
somebody (davem?) applied your divide-by-zero patch to the mainline
kernel.
My initial comment is that we will want to work to eliminate these
ifdefs. Other comments will follow.
Thanks to Intel for these efforts!
Jeff
prev parent reply other threads:[~2003-03-20 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 15:14 [patch] (0/8) Adding 802.3ad support to bonding Shmulik Hen
2003-03-20 16:56 ` Jeff Garzik [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=20030320165618.GB8256@gtf.org \
--to=jgarzik@pobox.com \
--cc=bonding-announce@lists.sourceforge.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=hshmulik@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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).