From: Ido Schimmel <idosch@nvidia.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, vadimp@nvidia.com
Cc: vadimp@nvidia.com, rafael@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"open list:MELLANOX ETHERNET SWITCH DRIVERS"
<netdev@vger.kernel.org>
Subject: Re: [PATCH 2/2] thermal/drivers/mellanox: Use generic thermal_zone_get_trip() function
Date: Tue, 25 Oct 2022 13:32:17 +0300 [thread overview]
Message-ID: <Y1e7MRozZYSHgV0V@shredder> (raw)
In-Reply-To: <cb44e8f7-92f6-0756-a622-1128d830291c@linaro.org>
On Tue, Oct 25, 2022 at 09:02:23AM +0200, Daniel Lezcano wrote:
> Because I hope I can remove the ops->get_trip_ ops from thermal_ops
> structure before the end of this cycle.
OK. Vadim, any chance you can review the patch?
> May be you can consider moving the thermal driver into drivers/thermal?
I don't think it's worth the hassle (if possible at all). In practice,
this code is upstream for almost six years and IIRC we didn't have any
conflicts with the thermal tree. I don't expect conflicts this cycle
either.
next prev parent reply other threads:[~2022-10-25 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 7:32 [PATCH 1/2] thermal/drivers/iwlwifi: Use generic thermal_zone_get_trip() function Daniel Lezcano
2022-10-14 7:32 ` [PATCH 2/2] thermal/drivers/mellanox: " Daniel Lezcano
2022-10-18 6:28 ` Ido Schimmel
2022-10-25 7:02 ` Daniel Lezcano
2022-10-25 10:32 ` Ido Schimmel [this message]
2022-10-30 17:24 ` Vadim Pasternak
2022-11-06 18:13 ` Vadim Pasternak
2022-12-09 15:26 ` [thermal: thermal/next] " thermal-bot for Daniel Lezcano
2022-10-14 10:15 ` [PATCH 1/2] thermal/drivers/iwlwifi: " Kalle Valo
2022-10-14 10:21 ` Daniel Lezcano
2022-10-18 9:38 ` Greenman, Gregory
2022-10-19 6:04 ` Kalle Valo
2022-12-09 15:26 ` [thermal: thermal/next] wifi: iwlwifi: " thermal-bot for Daniel Lezcano
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=Y1e7MRozZYSHgV0V@shredder \
--to=idosch@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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.