From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <nikolay@cumulusnetworks.com>, <roopa@cumulusnetworks.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR
Date: Fri, 26 Jun 2020 09:33:47 +0200 [thread overview]
Message-ID: <20200626073349.3495526-1-horatiu.vultur@microchip.com> (raw)
This patch series extends MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR.
To allow the userspace to clear all MRP instances when is started. The
second patch in the series fix different sparse warnings.
v3:
- add the second patch to fix sparse warnings
v2:
- use list_for_each_entry_safe instead of list_for_each_entry_rcu
when deleting mrp instances
Horatiu Vultur (2):
bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR
bridge: mrp: Fix endian conversion and some other warnings
include/uapi/linux/if_bridge.h | 8 ++++++++
net/bridge/br_mrp.c | 17 ++++++++++++++++-
net/bridge/br_mrp_netlink.c | 26 ++++++++++++++++++++++++++
net/bridge/br_private.h | 2 +-
net/bridge/br_private_mrp.h | 3 ++-
5 files changed, 53 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-26 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 7:33 Horatiu Vultur [this message]
2020-06-26 7:33 ` [PATCH net-next v3 1/2] " Horatiu Vultur
2020-06-26 7:33 ` [PATCH net-next v3 2/2] bridge: mrp: Fix endian conversion and some other warnings Horatiu Vultur
2020-06-26 20:00 ` [PATCH net-next v3 0/2] bridge: mrp: Extend MRP netlink interface with IFLA_BRIDGE_MRP_CLEAR David Miller
2020-06-28 12:59 ` Horatiu Vultur
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=20200626073349.3495526-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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
all inboxes | Powered by JetHome®