From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
petrm@nvidia.com, jiri@nvidia.com, amcohen@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/7] mlxsw: Various updates
Date: Fri, 28 Jan 2022 03:30:12 +0000 [thread overview]
Message-ID: <164334061249.5963.14021766704763689043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127090226.283442-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Jan 2022 11:02:19 +0200 you wrote:
> This patchset contains miscellaneous updates for mlxsw. No user visible
> changes that I am aware of.
>
> Patches #1-#5 rework registration of internal traps in preparation of
> line cards support.
>
> Patch #6 improves driver resilience against a misbehaving device.
>
> [...]
Here is the summary with links:
- [net-next,1/7] mlxsw: spectrum: Set basic trap groups from an array
https://git.kernel.org/netdev/net-next/c/7aad5244f000
- [net-next,2/7] mlxsw: core: Move basic_trap_groups_set() call out of EMAD init code
https://git.kernel.org/netdev/net-next/c/74e0494d35ac
- [net-next,3/7] mlxsw: core: Move basic trap group initialization from spectrum.c
https://git.kernel.org/netdev/net-next/c/8ae89cf454b0
- [net-next,4/7] mlxsw: core: Move functions to register/unregister array of traps to core.c
https://git.kernel.org/netdev/net-next/c/981f1d18be40
- [net-next,5/7] mlxsw: core: Consolidate trap groups to a single event group
https://git.kernel.org/netdev/net-next/c/636d3ad23890
- [net-next,6/7] mlxsw: spectrum: Guard against invalid local ports
https://git.kernel.org/netdev/net-next/c/bcdfd615f83b
- [net-next,7/7] mlxsw: spectrum_acl: Allocate default actions for internal TCAM regions
https://git.kernel.org/netdev/net-next/c/ef14c298b5b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-28 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 9:02 [PATCH net-next 0/7] mlxsw: Various updates Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 1/7] mlxsw: spectrum: Set basic trap groups from an array Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 2/7] mlxsw: core: Move basic_trap_groups_set() call out of EMAD init code Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 3/7] mlxsw: core: Move basic trap group initialization from spectrum.c Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 4/7] mlxsw: core: Move functions to register/unregister array of traps to core.c Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 5/7] mlxsw: core: Consolidate trap groups to a single event group Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 6/7] mlxsw: spectrum: Guard against invalid local ports Ido Schimmel
2022-01-27 9:02 ` [PATCH net-next 7/7] mlxsw: spectrum_acl: Allocate default actions for internal TCAM regions Ido Schimmel
2022-01-28 3:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-09 8:59 [PATCH net-next 0/7] mlxsw: Various updates Ido Schimmel
2018-08-09 17:37 ` David Miller
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=164334061249.5963.14021766704763689043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--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.