From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: Jori Koolstra <jkoolstra@xs4all.nl>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
driver-core@lists.linux.dev
Subject: Re: [PATCH] thermal: change thermal_class to a const struct
Date: Mon, 24 Aug 2026 18:56:05 +0200 [thread overview]
Message-ID: <2026082411-flask-rewire-434f@gregkh> (raw)
In-Reply-To: <CAJZ5v0i0PQEMTOT6UqWO87jCdV539ns-KcP69n++eQsz_NG0zA@mail.gmail.com>
On Mon, Aug 24, 2026 at 06:09:33PM +0200, Rafael J. Wysocki (Intel) wrote:
> On Tue, Aug 11, 2026 at 8:17 AM Jori Koolstra <jkoolstra@xs4all.nl> wrote:
> >
> > The class_create() call has been deprecated in favor of class_register()
> > as the driver core now allows for a struct class to be in read-only
> > memory. Change thermal_class to be a const struct class and drop the
> > class_create() call.
>
> This has been deliberately changed the other way around not too long
> ago, in commit
>
> 34f54003643e thermal/core: Allocate the thermal class dynamically
>
> and it was then argued that it would be better to allocate the class
> dynamically.
>
> You seem to have a differing opinion.
>
> Is there any plan to remove class_create() from the kernel? If there
> isn't, I'd rather stop this back-and-forth dance and leave the code
> as-is.
Yes, class_create() is going away. I didn't notice commit 34f54003643e,
but that's the wrong thing to do here. We should just revert that
instead.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-24 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 6:15 [PATCH] thermal: change thermal_class to a const struct Jori Koolstra
2026-08-24 16:09 ` Rafael J. Wysocki (Intel)
2026-08-24 16:56 ` Greg Kroah-Hartman [this message]
2026-08-24 16:58 ` Greg Kroah-Hartman
2026-08-24 17:04 ` Rafael J. Wysocki (Intel)
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=2026082411-flask-rewire-434f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=daniel.lezcano@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=jkoolstra@xs4all.nl \
--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 \
/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