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,
mlxsw@nvidia•com
Subject: Re: [PATCH net v2 0/3] mlxsw: Fixes
Date: Sat, 20 Apr 2024 03:50:32 +0000 [thread overview]
Message-ID: <171358503274.31195.14039830410285866432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1713446092.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 18 Apr 2024 15:46:05 +0200 you wrote:
> This patchset fixes the following issues:
>
> - During driver de-initialization the driver unregisters the EMAD
> response trap by setting its action to DISCARD. However the manual
> only permits TRAP and FORWARD, and future firmware versions will
> enforce this.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] mlxsw: core: Unregister EMAD trap using FORWARD action
https://git.kernel.org/netdev/net/c/976c44af4814
- [net,v2,2/3] mlxsw: core_env: Fix driver initialization with old firmware
https://git.kernel.org/netdev/net/c/7e2050a83663
- [net,v2,3/3] mlxsw: pci: Fix driver initialization with old firmware
https://git.kernel.org/netdev/net/c/773501d01e6b
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:[~2024-04-20 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 13:46 [PATCH net v2 0/3] mlxsw: Fixes Petr Machata
2024-04-18 13:46 ` [PATCH net v2 1/3] mlxsw: core: Unregister EMAD trap using FORWARD action Petr Machata
2024-04-18 13:46 ` [PATCH net v2 2/3] mlxsw: core_env: Fix driver initialization with old firmware Petr Machata
2024-04-18 17:55 ` Simon Horman
2024-04-18 13:46 ` [PATCH net v2 3/3] mlxsw: pci: " Petr Machata
2024-04-20 3: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=171358503274.31195.14039830410285866432.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mlxsw@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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