From: Simon Horman <simon.horman@corigine.com>
To: Petr Machata <petrm@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ido Schimmel <idosch@nvidia.com>,
Vadim Pasternak <vadimp@nvidia.com>,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 3/3] mlxsw: core_thermal: Simplify transceiver module get_temp() callback
Date: Sun, 2 Apr 2023 13:29:21 +0200 [thread overview]
Message-ID: <ZClnETy6m4pFrHyV@corigine.com> (raw)
In-Reply-To: <e0cc8a345cb5051aa692422340d8810e99152c7e.1680272119.git.petrm@nvidia.com>
On Fri, Mar 31, 2023 at 04:17:32PM +0200, Petr Machata wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The get_temp() callback of a thermal zone associated with a transceiver
> module no longer needs to read the temperature thresholds of the module.
> Therefore, simplify the callback by only reading the temperature.
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> Reviewed-by: Vadim Pasternak <vadimp@nvidia.com>
> Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-04-02 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:17 [PATCH net-next 0/3] mlxsw: Use static trip points for transceiver modules Petr Machata
2023-03-31 14:17 ` [PATCH net-next 1/3] mlxsw: core_thermal: " Petr Machata
2023-04-01 20:28 ` Daniel Lezcano
2023-04-02 11:28 ` Simon Horman
2023-03-31 14:17 ` [PATCH net-next 2/3] mlxsw: core_thermal: Make mlxsw_thermal_module_init() void Petr Machata
2023-04-02 11:28 ` Simon Horman
2023-03-31 14:17 ` [PATCH net-next 3/3] mlxsw: core_thermal: Simplify transceiver module get_temp() callback Petr Machata
2023-04-02 11:29 ` Simon Horman [this message]
2023-04-02 12:50 ` [PATCH net-next 0/3] mlxsw: Use static trip points for transceiver modules patchwork-bot+netdevbpf
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=ZClnETy6m4pFrHyV@corigine.com \
--to=simon.horman@corigine.com \
--cc=daniel.lezcano@linaro.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 \
--cc=rafael@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.