Date: Tue, 10 Jun 2014 23:51:23 -0700 (PDT)
Message-Id: <20140610.235123.310487202447168937.davem@davemloft.net>
To: linus.luessing@web.de
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
        stephen@networkplumber.org, herbert@gondor.apana.org.au,
        linux-kernel@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCHv4 net-next 0/4] bridge: multicast snooping patches /
 exports
From: David Miller <davem@davemloft.net>
In-Reply-To: <1402158389-13239-1-git-send-email-linus.luessing@web.de>
References: <1402158389-13239-1-git-send-email-linus.luessing@web.de>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/