From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next 0/4] net: dsa: pass bridge device to drivers
Date: Tue, 23 Feb 2016 11:08:26 -0500 [thread overview]
Message-ID: <87fuwjcsud.fsf@ketchup.mtl.sfl> (raw)
In-Reply-To: <1455296981-27998-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Hi all,
Vivien Didelot <vivien.didelot@savoirfairelinux.com> writes:
> This patchset simplifies the DSA layer.
>
> A switch may support multiple bridges with the same hardware VLAN. Thus a check
> such as dsa_bridge_check_vlan_range must be moved from the DSA layer to the
> concerned driver.
>
> The first purpose of this patchset is to help moving this check to the
> mv88e6xxx driver, which is the only one affected at the moment.
>
> To do that, pass directly the bridge net_device structure down to the DSA
> drivers, instead of calculating a bitmask of bridge members.
>
> The second purpose is to prepare the replacement of the complex
> port_vlan_getnext approach. A second patchset is ready to follow, implementing
> port_vlan_dump and thus simplifying the DSA slave code one more time.
>
> Note that this patchset applies on top of https://lkml.org/lkml/2016/2/5/532.
The dependent fix from net is now merged into net-next, which makes this
patchset apply well. I'm sending the second patchset right away.
Thanks,
-v
next prev parent reply other threads:[~2016-02-23 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 17:09 [PATCH net-next 0/4] net: dsa: pass bridge device to drivers Vivien Didelot
2016-02-12 17:09 ` [PATCH net-next 1/4] net: dsa: mv88e6xxx: add port private structure Vivien Didelot
2016-02-12 17:09 ` [PATCH net-next 2/4] net: dsa: pass bridge down to drivers Vivien Didelot
2016-02-13 18:42 ` Florian Fainelli
2016-02-12 17:09 ` [PATCH net-next 3/4] net: dsa: mv88e6xxx: check hardware VLAN in use Vivien Didelot
2016-02-13 18:17 ` Sergei Shtylyov
2016-02-13 19:53 ` Vivien Didelot
2016-02-13 20:08 ` Sergei Shtylyov
2016-02-12 17:09 ` [PATCH net-next 4/4] net: dsa: remove dsa_bridge_check_vlan_range Vivien Didelot
2016-02-23 16:08 ` Vivien Didelot [this message]
2016-02-23 19:53 ` [PATCH net-next 0/4] net: dsa: pass bridge device to drivers David Miller
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=87fuwjcsud.fsf@ketchup.mtl.sfl \
--to=vivien.didelot@savoirfairelinux.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).