From: Florian Fainelli <f.fainelli@gmail.com>
To: Russell King <rmk+kernel@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/3] net: dsa: add support for bridge flags
Date: Wed, 20 Feb 2019 13:46:12 -0800 [thread overview]
Message-ID: <21f30e49-06bb-0a6c-08cd-e8fb3db59a8e@gmail.com> (raw)
In-Reply-To: <E1gwYuI-0001aX-2u@rmk-PC.armlinux.org.uk>
On 2/20/19 12:55 PM, Russell King wrote:
> The Linux bridge implementation allows various properties of the bridge
> to be controlled, such as flooding unknown unicast and multicast frames.
> This patch adds the necessary DSA infrastructure to allow the Linux
> bridge support to control these properties for DSA switches.
>
> Reviewed-by: Vivien Didelot <vivien.didelot@gmail.com>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2019-02-20 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 20:55 [PATCH net-next v4 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
2019-02-20 20:55 ` [PATCH net-next v4 1/3] net: dsa: add support for bridge flags Russell King
2019-02-20 21:46 ` Florian Fainelli [this message]
2019-02-20 23:18 ` Florian Fainelli
2019-02-20 23:23 ` Russell King - ARM Linux admin
2019-02-20 20:55 ` [PATCH net-next v4 2/3] net: dsa: mv88e6xxx: " Russell King
2019-02-20 21:51 ` Florian Fainelli
2019-02-20 22:23 ` Vivien Didelot
2019-02-20 20:56 ` [PATCH net-next v4 3/3] net: dsa: enable flooding for bridge ports Russell King
2019-02-20 21:51 ` Florian Fainelli
2019-02-20 22:29 ` Vivien Didelot
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=21f30e49-06bb-0a6c-08cd-e8fb3db59a8e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vivien.didelot@gmail.com \
/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).