From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
UNGLinuxDriver@microchip.com
Subject: [PATCH v2 net-next 0/3] Small ocelot VLAN improvements
Date: Thu, 19 Aug 2021 20:40:05 +0300 [thread overview]
Message-ID: <20210819174008.2268874-1-vladimir.oltean@nxp.com> (raw)
This small series propagates some VLAN restrictions via netlink extack
and creates some helper functions instead of open-coding VLAN table
manipulations from multiple places.
This is split from the larger "DSA FDB isolation" series, hence the v2
tag:
https://patchwork.kernel.org/project/netdevbpf/cover/20210818120150.892647-1-vladimir.oltean@nxp.com/
Vladimir Oltean (3):
net: mscc: ocelot: transmit the "native VLAN" error via extack
net: mscc: ocelot: transmit the VLAN filtering restrictions via extack
net: mscc: ocelot: use helpers for port VLAN membership
drivers/net/dsa/ocelot/felix.c | 10 ++--
drivers/net/ethernet/mscc/ocelot.c | 73 ++++++++++++++++----------
drivers/net/ethernet/mscc/ocelot_net.c | 38 ++++++++------
include/soc/mscc/ocelot.h | 5 +-
4 files changed, 76 insertions(+), 50 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-19 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 17:40 Vladimir Oltean [this message]
2021-08-19 17:40 ` [PATCH v2 net-next 1/3] net: mscc: ocelot: transmit the "native VLAN" error via extack Vladimir Oltean
2021-08-19 17:40 ` [PATCH v2 net-next 2/3] net: mscc: ocelot: transmit the VLAN filtering restrictions " Vladimir Oltean
2021-08-19 17:40 ` [PATCH v2 net-next 3/3] net: mscc: ocelot: use helpers for port VLAN membership Vladimir Oltean
2021-08-20 13:50 ` [PATCH v2 net-next 0/3] Small ocelot VLAN improvements patchwork-bot+netdevbpf
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=20210819174008.2268874-1-vladimir.oltean@nxp.com \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.