From: David Miller <davem@davemloft.net>
To: fubar@us.ibm.com
Cc: monis@voltaire.com, rdreier@cisco.com,
bonding-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: clean muticast addresses when bevice changes type
Date: Thu, 16 Jul 2009 18:09:07 -0700 (PDT) [thread overview]
Message-ID: <20090716.180907.268411887.davem@davemloft.net> (raw)
In-Reply-To: <29772.1247777879@death.nxdomain.ibm.com>
From: Jay Vosburgh <fubar@us.ibm.com>
Date: Thu, 16 Jul 2009 13:57:59 -0700
>>Signed-off-by: Moni Shoua <monis@voltaire.com>
>
> I checked the discussion noted in a separate email, and the
> rationale seems reasonable.
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Applied.
prev parent reply other threads:[~2009-07-17 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 14:56 [PATCH] bonding: clean muticast addresses when bevice changes type Moni Shoua
2009-07-15 15:03 ` Moni Shoua
2009-07-16 20:57 ` Jay Vosburgh
2009-07-17 1:09 ` David Miller [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=20090716.180907.268411887.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=monis@voltaire.com \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.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).