lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gj33W-2FOswYoBLQQyTj0wr_EuMUdLiL_tdt4t=ss-jg@mail.gmail.com>
Date: Fri, 29 Aug 2025 21:09:20 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linux PM <linux-pm@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, 
	Sudeep Holla <sudeep.holla@....com>, Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > Hi All,
> > >
> > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> >
> > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > older kernels as well?

So do you want me to resend these patches with suitable Cc: stable tags?

Alternatively, I can just apply them with the tags and route them
through my tree, whatever you prefer.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ