From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <nikolay@cumulusnetworks.com>, <roopa@cumulusnetworks.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>, <netdev@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net v2 0/2] bridge: mrp: Update MRP_PORT_ROLE
Date: Tue, 23 Jun 2020 11:05:39 +0200 [thread overview]
Message-ID: <20200623090541.2964760-1-horatiu.vultur@microchip.com> (raw)
This patch series does the following:
- fixes the enum br_mrp_port_role_type. It removes the port role none(0x2)
because this is in conflict with the standard. The standard defines the
interconnect port role as value 0x2.
- adds checks regarding current defined port roles: primary(0x0) and
secondary(0x1).
v2:
- add the validation code when setting the port role.
Horatiu Vultur (2):
bridge: uapi: mrp: Fix MRP_PORT_ROLE
bridge: mrp: Validate when setting the port role
include/uapi/linux/mrp_bridge.h | 1 -
net/bridge/br_mrp.c | 10 ++++++++--
2 files changed, 8 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-23 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:05 Horatiu Vultur [this message]
2020-06-23 9:05 ` [PATCH net v2 1/2] bridge: uapi: mrp: Fix MRP_PORT_ROLE Horatiu Vultur
2020-06-23 9:05 ` [PATCH net v2 2/2] bridge: mrp: Validate when setting the port role Horatiu Vultur
2020-06-23 21:38 ` [PATCH net v2 0/2] bridge: mrp: Update MRP_PORT_ROLE David Miller
2020-06-24 11:31 ` Horatiu Vultur
2020-06-24 15:24 ` Vladimir Oltean
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=20200623090541.2964760-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@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®