From: "Linus Lüssing" <linus.luessing@web.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Linus Lüssing" <linus.luessing@web.de>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] bridge: prevent flooding IPv6 packets that do not have a listener
Date: Mon, 22 Jul 2013 22:05:11 +0200 [thread overview]
Message-ID: <20130722200511.GA5852@Linus-Debian> (raw)
In-Reply-To: <1371815638-5618-1-git-send-email-linus.luessing@web.de>
Hi Herbert,
Were there any reasons I might not be aware of which prevented you
from adding the same change you introduced in
"bridge: Only flood unregistered groups to routers" for IPv6, too?
If not and if no one else comes up with any objection, then I'd
still be happy if this patch could find its way upstream :).
Cheers, Linus
prev parent reply other threads:[~2013-07-22 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 11:53 [PATCH] bridge: prevent flooding IPv6 packets that do not have a listener Linus Lüssing
2013-07-22 20:05 ` Linus Lüssing [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=20130722200511.GA5852@Linus-Debian \
--to=linus.luessing@web.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).