From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <jiri@resnulli.us>, <ivecera@redhat.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <roopa@cumulusnetworks.com>,
<nikolay@cumulusnetworks.com>, <andrew@lunn.ch>,
<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH v2 0/3] bridge: mrp: Add br_mrp_unique_ifindex function
Date: Thu, 21 May 2020 23:19:04 +0000 [thread overview]
Message-ID: <20200521231907.3564679-1-horatiu.vultur@microchip.com> (raw)
This patch series adds small fixes to MRP implementation.
The following are fixed in this patch series:
- now is not allow to add the same port to multiple MRP rings
- remove unused variable
- restore the port state according to the bridge state when the MRP instance
is deleted
v2:
- use rtnl_dereference instead of rcu_dereference in the first patch
Horatiu Vultur (3):
bridge: mrp: Add br_mrp_unique_ifindex function
switchdev: mrp: Remove the variable mrp_ring_state
bridge: mrp: Restore port state when deleting MRP instance
include/net/switchdev.h | 1 -
net/bridge/br_mrp.c | 38 ++++++++++++++++++++++++++++++++++----
2 files changed, 34 insertions(+), 5 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-21 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 23:19 Horatiu Vultur [this message]
2020-05-21 23:19 ` [PATCH v2 1/3] bridge: mrp: Add br_mrp_unique_ifindex function Horatiu Vultur
2020-05-21 23:19 ` [PATCH v2 2/3] switchdev: mrp: Remove the variable mrp_ring_state Horatiu Vultur
2020-05-21 23:19 ` [PATCH v2 3/3] bridge: mrp: Restore port state when deleting MRP instance Horatiu Vultur
2020-05-22 23:17 ` [PATCH v2 0/3] bridge: mrp: Add br_mrp_unique_ifindex function 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=20200521231907.3564679-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--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;
as well as URLs for NNTP newsgroup(s).