From: David Miller <davem@davemloft.net>
To: linus.luessing@c0d3.blue
Cc: b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
yoshfuji@linux-ipv6.org, stephen@networkplumber.org,
herbert@gondor.apana.org.au, tom@herbertland.com
Subject: Re: [PATCHv3 net-next 0/2] Exporting IGMP/MLD checking from bridge code
Date: Mon, 04 May 2015 14:49:44 -0400 (EDT) [thread overview]
Message-ID: <20150504.144944.1896578946813579544.davem@davemloft.net> (raw)
In-Reply-To: <1430568067-6912-1-git-send-email-linus.luessing@c0d3.blue>
From: Linus Lüssing <linus.luessing@c0d3.blue>
Date: Sat, 2 May 2015 14:01:05 +0200
> The multicast optimizations in batman-adv are yet only usable and
> enabled in non-bridged scenarios. To be able to support bridged setups
> batman-adv needs to be able to detect IGMP/MLD queriers and reports on
> mesh nodes without bridges, too. See the following link for details:
>
> http://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-listener-reports
>
> To avoid duplicate code between the bridge and batman-adv, the IGMP/MLD
> message validation code is moved from the bridge to the IPv4/IPv6 stack.
>
> On the way, some refactoring to increase readability and to iron out
> some subtle differences between the IGMP and MLD parsing code is done.
Series applied, thanks.
prev parent reply other threads:[~2015-05-04 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 12:01 Linus Lüssing
2015-05-02 12:01 ` [PATCHv3 net-next 1/2] bridge: multicast: call skb_checksum_{simple_, }validate Linus Lüssing
2015-05-04 16:10 ` Stephen Hemminger
2015-05-02 12:01 ` [PATCHv3 net-next 2/2] net: Export IGMP/MLD message validation code Linus Lüssing
2015-05-04 18:49 ` 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=20150504.144944.1896578946813579544.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@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tom@herbertland.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®