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] mlxsw: Maintain candidate RIFs
Date: Sat, 24 Jun 2023 02:10:21 +0000 [thread overview]
Message-ID: <168757262195.25434.17193714700819777953.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1687438411.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Jun 2023 15:33:01 +0200 you wrote:
> The mlxsw driver currently makes the assumption that the user applies
> configuration in a bottom-up manner. Thus netdevices need to be added to
> the bridge before IP addresses are configured on that bridge or SVI added
> on top of it. Enslaving a netdevice to another netdevice that already has
> uppers is in fact forbidden by mlxsw for this reason. Despite this safety,
> it is rather easy to get into situations where the offloaded configuration
> is just plain wrong.
>
> [...]
Here is the summary with links:
- [net-next,1/8] mlxsw: spectrum_router: Add extack argument to mlxsw_sp_lb_rif_init()
https://git.kernel.org/netdev/net-next/c/ebbd17ce297a
- [net-next,2/8] mlxsw: spectrum_router: Use mlxsw_sp_ul_rif_get() to get main VRF LB RIF
https://git.kernel.org/netdev/net-next/c/f3c85eed1ac3
- [net-next,3/8] mlxsw: spectrum_router: Maintain a hash table of CRIFs
https://git.kernel.org/netdev/net-next/c/4796c287b70a
- [net-next,4/8] mlxsw: spectrum_router: Maintain CRIF for fallback loopback RIF
https://git.kernel.org/netdev/net-next/c/78126cfd5dc9
- [net-next,5/8] mlxsw: spectrum_router: Link CRIFs to RIFs
https://git.kernel.org/netdev/net-next/c/aa21242b07a8
- [net-next,6/8] mlxsw: spectrum_router: Use router.lb_crif instead of .lb_rif_index
https://git.kernel.org/netdev/net-next/c/bdc0b78e79a6
- [net-next,7/8] mlxsw: spectrum_router: Split nexthop finalization to two stages
https://git.kernel.org/netdev/net-next/c/a285d664236e
- [net-next,8/8] mlxsw: spectrum_router: Track next hops at CRIFs
https://git.kernel.org/netdev/net-next/c/9464a3d68ea9
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-06-24 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 13:33 [PATCH net-next 0/8] mlxsw: Maintain candidate RIFs Petr Machata
2023-06-22 13:33 ` [PATCH net-next 1/8] mlxsw: spectrum_router: Add extack argument to mlxsw_sp_lb_rif_init() Petr Machata
2023-06-22 13:33 ` [PATCH net-next 2/8] mlxsw: spectrum_router: Use mlxsw_sp_ul_rif_get() to get main VRF LB RIF Petr Machata
2023-06-22 13:33 ` [PATCH net-next 3/8] mlxsw: spectrum_router: Maintain a hash table of CRIFs Petr Machata
2023-06-22 13:33 ` [PATCH net-next 4/8] mlxsw: spectrum_router: Maintain CRIF for fallback loopback RIF Petr Machata
2023-06-22 13:33 ` [PATCH net-next 5/8] mlxsw: spectrum_router: Link CRIFs to RIFs Petr Machata
2023-06-22 13:33 ` [PATCH net-next 6/8] mlxsw: spectrum_router: Use router.lb_crif instead of .lb_rif_index Petr Machata
2023-06-22 13:33 ` [PATCH net-next 7/8] mlxsw: spectrum_router: Split nexthop finalization to two stages Petr Machata
2023-06-22 13:33 ` [PATCH net-next 8/8] mlxsw: spectrum_router: Track next hops at CRIFs Petr Machata
2023-06-24 2: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=168757262195.25434.17193714700819777953.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 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).