The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Sasha Levin <sashal@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: PM: Avoid attaching ACPI PM domain to certain devices
Date: Thu, 12 Dec 2019 18:58:35 +0100	[thread overview]
Message-ID: <1834000.7vQ4Mp1vVU@kreacher> (raw)
In-Reply-To: <20191211163643.CAFFC214D8@mail.kernel.org>

On Wednesday, December 11, 2019 5:36:43 PM CET Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: e5cc8ef31267 ("ACPI / PM: Provide ACPI PM callback routines for subsystems").
> 
> The bot has tested the following trees: v5.4.2, v5.3.15, v4.19.88, v4.14.158, v4.9.206, v4.4.206.
> 
> v5.4.2: Build OK!
> v5.3.15: Build OK!
> v4.19.88: Build OK!
> v4.14.158: Failed to apply! Possible dependencies:
>     001d50c9a14f ("PM / Domains: Remove obsolete "samsung,power-domain" check")
>     919b7308fcc4 ("PM / Domains: Allow a better error handling of dev_pm_domain_attach()")
> 
> v4.9.206: Failed to apply! Possible dependencies:
>     001d50c9a14f ("PM / Domains: Remove obsolete "samsung,power-domain" check")
>     34994692216b ("PM / Domains: Do not print PM domain add error message if EPROBE_DEFER")
>     35241d12f750 ("PM / Domains: Abstract genpd locking")
>     59d65b73a23c ("PM / Domains: Make genpd state allocation dynamic")
>     72038df3c580 ("PM / Domains: Fix error path during attach in genpd")
>     919b7308fcc4 ("PM / Domains: Allow a better error handling of dev_pm_domain_attach()")
> 
> v4.4.206: Failed to apply! Possible dependencies:
>     001d50c9a14f ("PM / Domains: Remove obsolete "samsung,power-domain" check")
>     0106ef5146f9 ("PM / domains: fix lockdep issue for all subdomains")
>     076395cae203 ("PM / Domains: Propagate start and restore errors during runtime resume")
>     1f7371b2a5fa ("drm/amd/powerplay: add basic powerplay framework")
>     25030321ba28 ("drm/amd: add pm domain for ACP IP sub blocks")
>     288912cb95d1 ("drm/amdgpu: use $(src) in Makefile (v2)")
>     34994692216b ("PM / Domains: Do not print PM domain add error message if EPROBE_DEFER")
>     35241d12f750 ("PM / Domains: Abstract genpd locking")
>     39dd0f234fc3 ("PM / Domains: Allow genpd to power on during system PM phases")
>     3fe577107ccf ("PM / Domains: Add support for removing PM domains")
>     4d23a5e84806 ("PM / Domains: Allow runtime PM during system PM phases")
>     53af16f79fbc ("PM / Domains: Silence compiler warning for an unused function")
>     59d65b73a23c ("PM / Domains: Make genpd state allocation dynamic")
>     624c8df7d282 ("PM / Domains: Remove redundant pm_runtime_get|put*() in pm_genpd_prepare()")
>     72038df3c580 ("PM / Domains: Fix error path during attach in genpd")
>     7eb231c337e0 ("PM / Domains: Convert pm_genpd_init() to return an error code")
>     8f9945558785 ("drm/amdgpu/acp: fix resume on CZ systems with AZ audio")
>     919b7308fcc4 ("PM / Domains: Allow a better error handling of dev_pm_domain_attach()")
>     a8fe58cec351 ("drm/amd: add ACP driver support")
>     cdb300a041f5 ("PM / Domains: Fix potential deadlock while adding/removing subdomains")
>     fc5cbf0c94b6 ("PM / Domains: Support for multiple states")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

This has been present in linux-next for some time and the commit carries a Cc: stable
tag.  No need to do anything special AFAICS.

Thanks!




      parent reply	other threads:[~2019-12-12 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  1:54 [PATCH] ACPI: PM: Avoid attaching ACPI PM domain to certain devices Rafael J. Wysocki
2019-12-04 14:04 ` Zhang Rui
2019-12-05 17:32   ` Todd Brandt
2019-12-09 22:34     ` Todd Brandt
2019-12-09 23:03       ` Rafael J. Wysocki
     [not found] ` <20191211163643.CAFFC214D8@mail.kernel.org>
2019-12-12 17:58   ` Rafael J. Wysocki [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=1834000.7vQ4Mp1vVU@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@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