netdev - Re: [PATCHv4 net-next 0/4] bridge: multicast snooping patches / exports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 Jun 2014 23:51:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linus.luessing@....de
Cc:	netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
	stephen@...workplumber.org, herbert@...dor.apana.org.au,
	linux-kernel@...r.kernel.org, b.a.t.m.a.n@...ts.open-mesh.org
Subject: Re: [PATCHv4 net-next 0/4] bridge: multicast snooping patches /
 exports

From: Linus Lüssing <linus.luessing@....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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html