From: David Miller <davem@davemloft.net>
To: linus.luessing@web.de
Cc: b.a.t.m.a.n@lists.open-mesh.org, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCHv4 net-next 0/4] bridge: multicast snooping patches / exports
Date: Tue, 10 Jun 2014 23:51:23 -0700 (PDT) [thread overview]
Message-ID: <20140610.235123.310487202447168937.davem@davemloft.net> (raw)
In-Reply-To: <1402158389-13239-1-git-send-email-linus.luessing@web.de>
From: Linus Lüssing <linus.luessing@web.de>
Date: Sat, 7 Jun 2014 18:26:25 +0200
> The first patch is simply a cosmetic patch. So far I (and maybe others
> too?) have been regularly confusing these two structs, therefore I'd
> suggest renaming them and therefore making the follow-up patches easier
> to understand and nicer to fit in.
>
> The second patch fixes a minor issue, but probably not worth for stable.
>
> On the other hand the first two patches are also preparations for the
> third and fourth patch:
>
> These two patches are exporting functionality needed to marry the bridge
> multicast snooping with the batman-adv multicast optimizations recently
> added for the 3.15 kernel, allowing to use these optimzations in common
> setups having a bridge on top of e.g. bat0, too. So far these bridged
> setups would fall back to simple flooding through the batman-adv mesh
> network for any multicast packet entering bat0.
Series applied, thank you.
prev parent reply other threads:[~2014-06-11 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 16:26 [PATCHv4 net-next 0/4] bridge: multicast snooping patches / exports Linus Lüssing
2014-06-07 16:26 ` [PATCHv4 net-next 1/4] bridge: rename struct bridge_mcast_query/querier Linus Lüssing
2014-06-07 16:26 ` [PATCHv4 net-next 2/4] bridge: adhere to querier election mechanism specified by RFCs Linus Lüssing
2014-06-07 16:26 ` [PATCHv4 net-next 3/4] bridge: add export of multicast database adjacent to net_dev Linus Lüssing
2014-06-07 16:26 ` [PATCHv4 net-next 4/4] bridge: memorize and export selected IGMP/MLD querier port Linus Lüssing
2014-06-11 6:51 ` 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=20140610.235123.310487202447168937.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bridge@lists.linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linus.luessing@web.de \
--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).