From: Jeff Garzik <jeff@garzik.org>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] bonding: only receive ARPs for us
Date: Fri, 02 Mar 2007 20:26:08 -0500 [thread overview]
Message-ID: <45E8CEB0.3070204@garzik.org> (raw)
In-Reply-To: <200703010103.l2113R22030799@death.nxdomain.ibm.com>
Jay Vosburgh wrote:
> The ARP validation code only needs ARPs for the bonding device.
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
I seem to have lost the context of this. Did this get discussed, and
need further revision?
The three patches from 2/28/2007 look OK to me, and I just wanted to
make sure before applying them.
Jeff
next prev parent reply other threads:[~2007-03-03 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:03 [PATCH 2/3] bonding: only receive ARPs for us Jay Vosburgh
2007-03-03 1:26 ` Jeff Garzik [this message]
2007-03-03 1:38 ` [Bonding-devel] " Jay Vosburgh
2007-03-03 1:41 ` 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=45E8CEB0.3070204@garzik.org \
--to=jeff@garzik.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).