From: Vivien Didelot <vivien.didelot@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
f.fainelli@gmail.com, andrew@lunn.ch
Subject: [PATCH net-next v2 0/4] net: dsa: use switchdev attr and obj handlers
Date: Fri, 14 Jun 2019 13:49:18 -0400 [thread overview]
Message-ID: <20190614174922.2590-1-vivien.didelot@gmail.com> (raw)
This series reduces boilerplate in the handling of switchdev attribute and
object operations by using the switchdev_handle_* helpers, which check the
targeted devices and recurse into their lower devices.
This also brings back the ability to inspect operations targeting the bridge
device itself (where .orig_dev and .dev were originally the bridge device),
even though that is of no use yet and skipped by this series.
Changes in v2: Only VLAN and (non-host) MDB objects not directly targeting
the slave device are unsupported at the moment, so only skip these cases.
Vivien Didelot (4):
net: dsa: do not check orig_dev in vlan del
net: dsa: make cpu_dp non const
net: dsa: make dsa_slave_dev_check use const
net: dsa: use switchdev handle helpers
include/net/dsa.h | 2 +-
net/dsa/port.c | 9 ------
net/dsa/slave.c | 80 ++++++++++++++++++++---------------------------
3 files changed, 35 insertions(+), 56 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-14 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:49 Vivien Didelot [this message]
2019-06-14 17:49 ` [PATCH net-next v2 1/4] net: dsa: do not check orig_dev in vlan del Vivien Didelot
2019-06-14 17:49 ` [PATCH net-next v2 2/4] net: dsa: make cpu_dp non const Vivien Didelot
2019-06-14 17:49 ` [PATCH net-next v2 3/4] net: dsa: make dsa_slave_dev_check use const Vivien Didelot
2019-06-14 17:49 ` [PATCH net-next v2 4/4] net: dsa: use switchdev handle helpers Vivien Didelot
2019-06-15 3:20 ` [PATCH net-next v2 0/4] net: dsa: use switchdev attr and obj handlers 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=20190614174922.2590-1-vivien.didelot@gmail.com \
--to=vivien.didelot@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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
all inboxes | Powered by JetHome®