From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Lukasz Luba <lukasz.luba@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] thermal/core: Hardening the self-encapsulation
Date: Thu, 12 Oct 2023 23:13:43 +0200 [thread overview]
Message-ID: <dcafb275-40eb-4663-8ede-bf15546f83f6@linaro.org> (raw)
In-Reply-To: <CAJZ5v0gC4+Jam0a4KpEr7onydn8Sp8MkN2yzVxm0W9qDpmEoDw@mail.gmail.com>
On 12/10/2023 19:44, Rafael J. Wysocki wrote:
[ ... ]
>> Yes, we should but there is the series for nvidia (pointed in the
>> changelog) which need a slight refresh for the bindings AFAIR. That
>> series is since March 2023 and Thierry seems busy [1]. I'm holding the
>> hardening since then.
>>
>> So I don't know how to make progress on this? I was assuming we can
>> merge this series and let the compiler recall what has to be fixed.
>>
>> [1] https://lore.kernel.org/all/ZK14edZUih1kH_sZ@orome/
>>
>> and as soon as it is fixed, we convert the WARNING to ERROR :P
>
> To be honest, I'm not sure if anything needs to be done along the
> lines of this patch right now or even at all.
>
> The only concern here would be that some new drivers would include
> thermal_core.h while we were waiting for the remaining existing
> abusers to be fixed, but since this hasn't happened for the last 6
> months, I'm not worried.
>
> It would be good to add a notice to thermal_core.h that this file is
> for internal use in the thermal core only, though.
So this series will give a warning for the remaining nvidia driver but
Thierry just send the changes to get rid of the thermal_core.h (Thanks!)
AFAICT, the last user of the thermal_zone_device structure is the
int340x driver but the patch fixing the structure internal usage is
already in the bleeding edge (well perhaps one nit is missing for the trace)
As soon as the bindings are acked, then I can pick the patches from
Thierry which will end up in your tree. Then you can apply the current
series. And finally I'll send the last patch moving the thermal zone
device structure to the thermal_core.h. And we will be done with this part.
Having a compilation warning (I would prefer a more coercive error if we
agree on that) will help to not have to double check every time
thermal_core.h is not pulled in the drivers when patches are submitted.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2023-10-12 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 10:26 [PATCH 1/2] thermal/core: Hardening the self-encapsulation Daniel Lezcano
2023-10-12 10:26 ` [PATCH 2/2] thermal/core: Reorder the headers inclusion Daniel Lezcano
2023-10-13 8:05 ` Lukasz Luba
2023-10-12 12:01 ` [PATCH 1/2] thermal/core: Hardening the self-encapsulation Lukasz Luba
2023-10-12 13:14 ` Daniel Lezcano
2023-10-12 14:30 ` Thierry Reding
2023-10-12 17:44 ` Rafael J. Wysocki
2023-10-12 21:13 ` Daniel Lezcano [this message]
2023-10-13 9:43 ` Rafael J. Wysocki
2023-10-13 8:03 ` Lukasz Luba
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=dcafb275-40eb-4663-8ede-bf15546f83f6@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox