From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
amcohen@nvidia.com, shuah@kernel.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model
Date: Fri, 19 Aug 2022 04:00:56 +0000 [thread overview]
Message-ID: <166088165648.14408.6467742450991542889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1660747162.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 17 Aug 2022 17:28:24 +0200 you wrote:
> Amit Cohen writes:
>
> Commit 798661c73672 ("Merge branch 'mlxsw-unified-bridge-conversion-part-6'")
> converted mlxsw driver to use unified bridge model. In the legacy model,
> when a RIF was created / destroyed, it was firmware's responsibility to
> update it in the relevant FID classification records. In the unified bridge
> model, this responsibility moved to software.
>
> [...]
Here is the summary with links:
- [net-next,1/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge
https://git.kernel.org/netdev/net-next/c/2cd87cea7842
- [net-next,2/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge
https://git.kernel.org/netdev/net-next/c/3a5ddc886847
- [net-next,3/4] selftests: mlxsw: Add ingress RIF configuration test for VXLAN
https://git.kernel.org/netdev/net-next/c/cbeb6e1195d1
- [net-next,4/4] selftests: mlxsw: Add egress VID classification test
https://git.kernel.org/netdev/net-next/c/1623d5719fdf
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-08-19 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 15:28 [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model Petr Machata
2022-08-17 15:28 ` [PATCH net-next 1/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge Petr Machata
2022-08-17 15:28 ` [PATCH net-next 2/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge Petr Machata
2022-08-17 15:28 ` [PATCH net-next 3/4] selftests: mlxsw: Add ingress RIF configuration test for VXLAN Petr Machata
2022-08-17 15:28 ` [PATCH net-next 4/4] selftests: mlxsw: Add egress VID classification test Petr Machata
2022-08-19 4:00 ` 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=166088165648.14408.6467742450991542889.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
/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).