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,
danieller@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/8] selftests: New selftests for out-of-order-operations patches in mlxsw
Date: Wed, 02 Aug 2023 08:20:22 +0000 [thread overview]
Message-ID: <169096442287.23876.3228332853923657209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1690815746.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 31 Jul 2023 17:47:14 +0200 you wrote:
> In the past, the mlxsw driver made the assumption that the user applies
> configuration in a bottom-up manner. Thus netdevices needed to be added to
> the bridge before IP addresses were configured on that bridge or SVI added
> on top of it, because whatever happened before a netdevice was mlxsw upper
> was generally ignored by mlxsw. Recently, several patch series were pushed
> to introduce the bookkeeping and replays necessary to offload the full
> state, not just the immediate configuration step.
>
> [...]
Here is the summary with links:
- [net-next,1/8] selftests: router_bridge: Add remastering tests
https://git.kernel.org/netdev/net-next/c/eb1388553ef4
- [net-next,2/8] selftests: router_bridge_1d: Add a new selftest
https://git.kernel.org/netdev/net-next/c/0a06e0c1af97
- [net-next,3/8] selftests: router_bridge_vlan_upper: Add a new selftest
https://git.kernel.org/netdev/net-next/c/49e15dec8b90
- [net-next,4/8] selftests: router_bridge_lag: Add a new selftest
https://git.kernel.org/netdev/net-next/c/3f0c4e70a9ef
- [net-next,5/8] selftests: router_bridge_1d_lag: Add a new selftest
https://git.kernel.org/netdev/net-next/c/24e84656e432
- [net-next,6/8] selftests: mlxsw: rif_lag: Add a new selftest
https://git.kernel.org/netdev/net-next/c/4308967d98c3
- [net-next,7/8] selftests: mlxsw: rif_lag_vlan: Add a new selftest
https://git.kernel.org/netdev/net-next/c/6b3f46837c32
- [net-next,8/8] selftests: mlxsw: rif_bridge: Add a new selftest
https://git.kernel.org/netdev/net-next/c/67d5ffb9ed51
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:[~2023-08-02 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 15:47 [PATCH net-next 0/8] selftests: New selftests for out-of-order-operations patches in mlxsw Petr Machata
2023-07-31 15:47 ` [PATCH net-next 1/8] selftests: router_bridge: Add remastering tests Petr Machata
2023-07-31 15:47 ` [PATCH net-next 2/8] selftests: router_bridge_1d: Add a new selftest Petr Machata
2023-07-31 15:47 ` [PATCH net-next 3/8] selftests: router_bridge_vlan_upper: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 4/8] selftests: router_bridge_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 5/8] selftests: router_bridge_1d_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 6/8] selftests: mlxsw: rif_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 7/8] selftests: mlxsw: rif_lag_vlan: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 8/8] selftests: mlxsw: rif_bridge: " Petr Machata
2023-08-02 8:20 ` 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=169096442287.23876.3228332853923657209.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danieller@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.