From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jiri@nvidia.com, vadimp@nvidia.com, mlxsw@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next] mlxsw: core: Remove critical trip points from thermal zones
Date: Wed, 07 Apr 2021 21:40:09 +0000 [thread overview]
Message-ID: <161783160905.25121.369474007143495180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210406122733.773304-1-idosch@idosch.org>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 6 Apr 2021 15:27:33 +0300 you wrote:
> From: Vadim Pasternak <vadimp@nvidia.com>
>
> Disable software thermal protection by removing critical trip points
> from all thermal zones.
>
> The software thermal protection is redundant given there are two layers
> of protection below it in firmware and hardware. The first layer is
> performed by firmware, the second, in case firmware was not able to
> perform protection, by hardware.
> The temperature threshold set for hardware protection is always higher
> than for firmware.
>
> [...]
Here is the summary with links:
- [net-next] mlxsw: core: Remove critical trip points from thermal zones
https://git.kernel.org/netdev/net-next/c/d567fd6e82fa
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:[~2021-04-07 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 12:27 [PATCH net-next] mlxsw: core: Remove critical trip points from thermal zones Ido Schimmel
2021-04-07 21:40 ` 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=161783160905.25121.369474007143495180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--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.