All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm
Date: Thu, 28 Aug 2025 13:07:11 +0200	[thread overview]
Message-ID: <2025082851-progress-unsliced-ade4@gregkh> (raw)
In-Reply-To: <12749467.O9o76ZdvQC@rafael.j.wysocki>

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?

thanks,

greg k-h

  parent reply	other threads:[~2025-08-28 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 10:55 [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm Rafael J. Wysocki
2025-08-28 10:56 ` [PATCH v1 1/2] driver core: faux: Set power.no_pm for faux devices Rafael J. Wysocki
2025-08-28 10:59 ` [PATCH v1 2/2] driver core/PM: Set power.no_callbacks along with power.no_pm Rafael J. Wysocki
2025-08-28 11:07 ` Greg Kroah-Hartman [this message]
2025-08-28 11:20   ` [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm Rafael J. Wysocki
2025-08-29 19:09     ` Rafael J. Wysocki
2025-09-03 11:33       ` Rafael J. Wysocki
2025-09-06 11:53         ` Greg Kroah-Hartman
2025-09-06 11:53           ` Greg Kroah-Hartman
2025-09-06 15:14             ` Rafael J. Wysocki
2025-08-28 12:41 ` Sudeep Holla

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=2025082851-progress-unsliced-ade4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.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.