From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, petrm@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 00/10] mlxsw: A dedicated notifier block for router code
Date: Sun, 08 May 2022 10:50:14 +0000 [thread overview]
Message-ID: <165200701492.399.4822548195944966662.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220508080823.32154-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 8 May 2022 11:08:13 +0300 you wrote:
> Petr says:
>
> Currently all netdevice events are handled in the centralized notifier
> handler maintained by spectrum.c. Since a number of events are involving
> router code, spectrum.c needs to dispatch them to spectrum_router.c. The
> spectrum module therefore needs to know more about the router code than it
> should have, and there is are several API points through which the two
> modules communicate.
>
> [...]
Here is the summary with links:
- [net-next,01/10] mlxsw: spectrum: Tolerate enslaving of various devices to VRF
https://git.kernel.org/netdev/net-next/c/7cf0f96df1d8
- [net-next,02/10] mlxsw: spectrum_router: Add a dedicated notifier block
https://git.kernel.org/netdev/net-next/c/0a27cb1692de
- [net-next,03/10] mlxsw: spectrum: Move handling of VRF events to router code
https://git.kernel.org/netdev/net-next/c/4f8afb680f13
- [net-next,04/10] mlxsw: spectrum: Move handling of HW stats events to router code
https://git.kernel.org/netdev/net-next/c/f40e600b369e
- [net-next,05/10] mlxsw: spectrum: Move handling of router events to router code
https://git.kernel.org/netdev/net-next/c/ba81954cd526
- [net-next,06/10] mlxsw: spectrum: Move handling of tunnel events to router code
https://git.kernel.org/netdev/net-next/c/75ef4342282a
- [net-next,07/10] mlxsw: spectrum: Update a comment
https://git.kernel.org/netdev/net-next/c/05a8d7d4fadf
- [net-next,08/10] mlxsw: spectrum_router: Take router lock in router notifier handler
https://git.kernel.org/netdev/net-next/c/c353fb0d4c93
- [net-next,09/10] selftests: lib: Add a generic helper for obtaining HW stats
https://git.kernel.org/netdev/net-next/c/32fb67a3e7a6
- [net-next,10/10] selftests: forwarding: Add a tunnel-based test for L3 HW stats
https://git.kernel.org/netdev/net-next/c/813f97a26860
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-05-08 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 8:08 [PATCH net-next 00/10] mlxsw: A dedicated notifier block for router code Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 01/10] mlxsw: spectrum: Tolerate enslaving of various devices to VRF Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 02/10] mlxsw: spectrum_router: Add a dedicated notifier block Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 03/10] mlxsw: spectrum: Move handling of VRF events to router code Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 04/10] mlxsw: spectrum: Move handling of HW stats " Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 05/10] mlxsw: spectrum: Move handling of router " Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 06/10] mlxsw: spectrum: Move handling of tunnel " Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 07/10] mlxsw: spectrum: Update a comment Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 08/10] mlxsw: spectrum_router: Take router lock in router notifier handler Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 09/10] selftests: lib: Add a generic helper for obtaining HW stats Ido Schimmel
2022-05-08 8:08 ` [PATCH net-next 10/10] selftests: forwarding: Add a tunnel-based test for L3 " Ido Schimmel
2022-05-08 10: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=165200701492.399.4822548195944966662.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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.