From: patchwork-bot+netdevbpf@kernel.org
To: Casper Andersson <casper.casan@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: sparx5: Allow mdb entries to both CPU and ports
Date: Wed, 15 Jun 2022 12:10:13 +0000 [thread overview]
Message-ID: <165529501372.14672.2338931366774698659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220614092532.3273791-1-casper.casan@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 14 Jun 2022 11:25:32 +0200 you wrote:
> Allow mdb entries to be forwarded to CPU and be switched at the same
> time. Only remove entry when no port and the CPU isn't part of the group
> anymore.
>
> Signed-off-by: Casper Andersson <casper.casan@gmail.com>
> ---
> .../microchip/sparx5/sparx5_switchdev.c | 55 ++++++++++++-------
> 1 file changed, 35 insertions(+), 20 deletions(-)
Here is the summary with links:
- [net-next] net: sparx5: Allow mdb entries to both CPU and ports
https://git.kernel.org/netdev/net-next/c/fbb89d02e33a
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:[~2022-06-15 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:25 [PATCH net-next] net: sparx5: Allow mdb entries to both CPU and ports Casper Andersson
2022-06-15 9:38 ` Steen Hegelund
2022-06-15 12:10 ` 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=165529501372.14672.2338931366774698659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).