Linux Power Management development
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Chris Bainbridge <chris.bainbridge@gmail.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Saravana Kannan <saravanak@google.com>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v1 0/3] PM: sleep: Fixes related to aborted suspend handling
Date: Tue, 3 Jun 2025 16:28:53 +0000	[thread overview]
Message-ID: <124f27b1-e7b0-4cba-a1d5-8e7805fc9809@amd.com> (raw)
In-Reply-To: <6166108.lOV4Wx5bFT@rjwysocki.net>

On 6/3/25 11:16 AM, Rafael J. Wysocki wrote:
> Hi Everyone,
> 
> Recently merged updates of the PM core have introduced three issues that
> manifest themselves when system suspend is aborted and the patches in this
> series fix them.
> 
> Please refer to the patch changelogs for details.
> 
> Many thanks to Chris Bainbridge for reporting the issues and testing the
> fixes.
> 
> Thanks!
> 
> 
> 

I found one typo in a commit message in the series, but otherwise it 
looks good.

Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>

Here's a tag to include for closing the issue that this started at as well.

Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4280

      parent reply	other threads:[~2025-06-03 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 16:16 [PATCH v1 0/3] PM: sleep: Fixes related to aborted suspend handling Rafael J. Wysocki
2025-06-03 16:17 ` [PATCH v1 1/3] PM: sleep: Fix list splicing in device suspend error paths Rafael J. Wysocki
2025-06-03 16:19 ` [PATCH v1 2/3] PM: sleep: Fix power.is_suspended cleanup for direct-complete devices Rafael J. Wysocki
2025-06-03 16:21 ` [PATCH v1 3/3] PM: sleep: Add locking to dpm_async_resume_children() Rafael J. Wysocki
2025-06-03 16:27   ` Limonciello, Mario
2025-06-03 16:31     ` Rafael J. Wysocki
2025-06-03 16:28 ` Limonciello, Mario [this message]

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=124f27b1-e7b0-4cba-a1d5-8e7805fc9809@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=chris.bainbridge@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=saravanak@google.com \
    --cc=sudeep.holla@arm.com \
    --cc=ulf.hansson@linaro.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