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,
jiri@mellanox.com, vadimp@mellanox.com, mlxsw@nvidia.com,
vadimp@nvidia.com
Subject: Re: [PATCH net] mlxsw: core_thermal: Fix fan speed in maximum cooling state
Date: Sun, 19 Mar 2023 15:30:17 +0000 [thread overview]
Message-ID: <167923981709.9440.6818651030993497762.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <573c8b3049fadb8b7353986427aeee915cf182f3.1679065970.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 17 Mar 2023 16:32:59 +0100 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The cooling levels array is supposed to prevent the system fans from
> being configured below a 20% duty cycle as otherwise some of them get
> stuck at 0 RPM.
>
> Due to an off-by-one error, the last element in the array was not
> initialized, causing it to be set to zero, which in turn lead to fans
> being configured with a 0% duty cycle in maximum cooling state.
>
> [...]
Here is the summary with links:
- [net] mlxsw: core_thermal: Fix fan speed in maximum cooling state
https://git.kernel.org/netdev/net/c/6d206b1ea9f4
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-03-19 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:32 [PATCH net] mlxsw: core_thermal: Fix fan speed in maximum cooling state Petr Machata
2023-03-19 15:30 ` 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=167923981709.9440.6818651030993497762.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vadimp@mellanox.com \
--cc=vadimp@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.