Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Julian Haller <julian.haller@philips.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.4 1/2] hwmon: Introduce hwmon_device_register_for_thermal
Date: Wed, 22 Jun 2022 18:09:39 +0200	[thread overview]
Message-ID: <YrM+wxRWV+RFTfjY@kroah.com> (raw)
In-Reply-To: <20220622154454.GA1864037@roeck-us.net>

On Wed, Jun 22, 2022 at 08:44:54AM -0700, Guenter Roeck wrote:
> On Wed, Jun 22, 2022 at 05:39:50PM +0200, Julian Haller wrote:
> > > On Wed, Jun 22, 2022 at 04:49:01PM +0200, Julian Haller wrote:
> > > > From: Guenter Roeck <linux@roeck-us.net>
> > > > 
> > > > [ upstream commit e5d21072054fbadf41cd56062a3a14e447e8c22b ]
> > > > 
> > > > The thermal subsystem registers a hwmon driver without providing
> > > > chip or sysfs group information. This is for legacy reasons and
> > > > would be difficult to change. At the same time, we want to enforce
> > > > that chip information is provided when registering a hwmon device
> > > > using hwmon_device_register_with_info(). To enable this, introduce
> > > > a special API for use only by the thermal subsystem.
> > > > 
> > > > Acked-by: Rafael J . Wysocki <rafael@kernel.org>
> > > > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > > 
> > > What is the point of applying those patches to the 5.4 kernel ?
> > > This was intended for use with new code, not for stable releases.
> > > 
> > > Guenter
> > 
> > The upstream commit ddaefa209c4ac791c1262e97c9b2d0440c8ef1d5 ("hwmon: Make chip
> > parameter for with_info API mandatory") was backported to the 5.4 kernel as
> > part of v5.4.198, see commit 1ec0bc72f5dab3ab367ae5230cf6f212d805a225. This
> > breaks the hwmon device registration in the thermal drivers as these two
> > patches here have been left out. We either need to include them as well or
> > revert the original commit.
> > 
> > I'm also not sure why the original commit found its way into the 5.4 stable
> > branch.
> > 
> 
> I had complained about this backport to other branches before. That patch
> was not a bug fix, it was neither intended nor marked for stable releases,
> and it should be reverted from all stable branches.

Yes, that's not right, let me go revert that.  Odd that it only went
into 4.19 and 5.4, I think Sasha's scripts went wonky there...

thanks,

greg k-h

  reply	other threads:[~2022-06-22 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 14:49 [PATCH 5.4 1/2] hwmon: Introduce hwmon_device_register_for_thermal Julian Haller
2022-06-22 14:49 ` [PATCH 5.4 2/2] thermal/drivers/thermal_hwmon: Use hwmon_device_register_for_thermal() Julian Haller
2022-06-22 15:02 ` [PATCH 5.4 1/2] hwmon: Introduce hwmon_device_register_for_thermal Guenter Roeck
2022-06-22 15:39   ` Julian Haller
2022-06-22 15:44     ` Guenter Roeck
2022-06-22 16:09       ` Greg KH [this message]
2022-06-22 16:12         ` Sasha Levin

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=YrM+wxRWV+RFTfjY@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=julian.haller@philips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=stable@vger.kernel.org \
    /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