From: Petr Machata <petrm@nvidia•com>
To: "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>
Cc: "Rafael J. Wysocki" <rafael@kernel•org>,
Daniel Lezcano <daniel.lezcano@linaro•org>,
Ido Schimmel <idosch@nvidia•com>, Petr Machata <petrm@nvidia•com>,
Vadim Pasternak <vadimp@nvidia•com>, <mlxsw@nvidia•com>
Subject: [PATCH net-next 0/3] mlxsw: Use static trip points for transceiver modules
Date: Fri, 31 Mar 2023 16:17:29 +0200 [thread overview]
Message-ID: <cover.1680272119.git.petrm@nvidia.com> (raw)
Ido Schimmel writes:
See patch #1 for motivation and implementation details.
Patches #2-#3 are simple cleanups as a result of the changes in the
first patch.
Ido Schimmel (3):
mlxsw: core_thermal: Use static trip points for transceiver modules
mlxsw: core_thermal: Make mlxsw_thermal_module_init() void
mlxsw: core_thermal: Simplify transceiver module get_temp() callback
.../ethernet/mellanox/mlxsw/core_thermal.c | 165 ++++--------------
1 file changed, 36 insertions(+), 129 deletions(-)
--
2.39.0
next reply other threads:[~2023-03-31 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:17 Petr Machata [this message]
2023-03-31 14:17 ` [PATCH net-next 1/3] mlxsw: core_thermal: Use static trip points for transceiver modules 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
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=cover.1680272119.git.petrm@nvidia.com \
--to=petrm@nvidia$(echo .)com \
--cc=daniel.lezcano@linaro$(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=rafael@kernel$(echo .)org \
--cc=vadimp@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