From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: jiri@resnulli.us, ivecera@redhat.com, davem@davemloft.net,
kuba@kernel.org, roopa@nvidia.com, nikolay@nvidia.com,
rasmus.villemoes@prevas.dk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [PATCH net 0/2] bridge: mrp: Fix br_mrp_port_switchdev_set_state
Date: Tue, 09 Feb 2021 00:50:06 +0000 [thread overview]
Message-ID: <161283180691.7845.8705102282874367511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210206214734.1577849-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Sat, 6 Feb 2021 22:47:32 +0100 you wrote:
> Based on the discussion here[1], there was a problem with the function
> br_mrp_port_switchdev_set_state. The problem was that it was called
> both with BR_STATE* and BR_MRP_PORT_STATE* types. This patch series
> fixes this issue and removes SWITCHDEV_ATTR_ID_MRP_PORT_STAT because
> is not used anymore.
>
> [1] https://www.spinics.net/lists/netdev/msg714816.html
>
> [...]
Here is the summary with links:
- [net,1/2] bridge: mrp: Fix the usage of br_mrp_port_switchdev_set_state
https://git.kernel.org/netdev/net/c/b2bdba1cbc84
- [net,2/2] switchdev: mrp: Remove SWITCHDEV_ATTR_ID_MRP_PORT_STAT
https://git.kernel.org/netdev/net/c/059d2a100498
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-02-09 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 21:47 [PATCH net 0/2] bridge: mrp: Fix br_mrp_port_switchdev_set_state Horatiu Vultur
2021-02-06 21:47 ` [PATCH net 1/2] bridge: mrp: Fix the usage of br_mrp_port_switchdev_set_state Horatiu Vultur
2021-02-09 7:37 ` Rasmus Villemoes
2021-02-06 21:47 ` [PATCH net 2/2] switchdev: mrp: Remove SWITCHDEV_ATTR_ID_MRP_PORT_STAT Horatiu Vultur
2021-02-09 7:38 ` Rasmus Villemoes
2021-02-09 0:50 ` patchwork-bot+netdevbpf [this message]
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=161283180691.7845.8705102282874367511.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=horatiu.vultur@microchip.com \
--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@nvidia.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=roopa@nvidia.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).