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-next v2 0/3] mlxsw: Improvements
Date: Wed, 10 Jul 2024 02:10:32 +0000 [thread overview]
Message-ID: <172057743277.1917.11660224520323271282.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1720447210.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 8 Jul 2024 16:23:39 +0200 you wrote:
> This patchset contains assortments of improvements to the mlxsw driver.
> Please see individual patches for details.
>
> v2:
> - Patch #1:
> - changed to WARN_ONCE() with some prints
> - Patch #2:
> - call thermal_cooling_device_unregister() unconditionally and mention
> it in the commit message
> - Patch #3:
> - reword the commit message to reflect the fact that the change both
> suppresses a warning and avoid concurrent access
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] mlxsw: Warn about invalid accesses to array fields
https://git.kernel.org/netdev/net-next/c/b45c76e5f43f
- [net-next,v2,2/3] mlxsw: core_thermal: Report valid current state during cooling device registration
https://git.kernel.org/netdev/net-next/c/a22f3bc80075
- [net-next,v2,3/3] mlxsw: pci: Lock configuration space of upstream bridge during reset
https://git.kernel.org/netdev/net-next/c/0970836c348b
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-07-10 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 14:23 [PATCH net-next v2 0/3] mlxsw: Improvements Petr Machata
2024-07-08 14:23 ` [PATCH net-next v2 1/3] mlxsw: Warn about invalid accesses to array fields Petr Machata
2024-07-08 14:23 ` [PATCH net-next v2 2/3] mlxsw: core_thermal: Report valid current state during cooling device registration Petr Machata
2024-07-08 14:23 ` [PATCH net-next v2 3/3] mlxsw: pci: Lock configuration space of upstream bridge during reset Petr Machata
2024-07-09 8:50 ` [PATCH net-next v2 0/3] mlxsw: Improvements Przemek Kitszel
2024-07-10 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=172057743277.1917.11660224520323271282.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.