public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Peter Geis <pgwipeout@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH 5.15.y 1/3] soc: rockchip: power-domain: Manage resource conflicts with firmware
Date: Tue, 6 Jan 2026 10:43:20 -0800	[thread overview]
Message-ID: <aV1XyFtvNX1lZGBE@google.com> (raw)
In-Reply-To: <20260106181021.3109327-1-sashal@kernel.org>

On Tue, Jan 06, 2026 at 01:10:14PM -0500, Sasha Levin wrote:
> From: Brian Norris <briannorris@chromium.org>
> 
> [ Upstream commit defec178df76e0caadd4e8ef68f3d655a2088198 ]
[snip]

This is a fairly large change, and I don't think it really qualifies for
-stable. It's also incomplete on its own, as we'd need commit
2e691421a2c9 ("PM / devfreq: rk3399_dmc: Block PMU during transitions")
to really do anything.

> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Tested-by: Peter Geis <pgwipeout@gmail.com>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> Stable-dep-of: 73cb5f6eafb0 ("pmdomain: imx: Fix reference count leak in imx_gpc_probe()")

Huh? I don't see how commit 73cb5f6eafb0 is dependent on this change at
all.

Is this an errant attempt at automating some cherry-pick conflict? I'd
recommend reconsidering.

Same for the 5.10.y copy of this patch.

> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  drivers/soc/rockchip/pm_domains.c | 118 ++++++++++++++++++++++++++++++
>  include/soc/rockchip/pm_domains.h |  25 +++++++
>  2 files changed, 143 insertions(+)
>  create mode 100644 include/soc/rockchip/pm_domains.h

[...]


Brian

      parent reply	other threads:[~2026-01-06 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 11:46 FAILED: patch "[PATCH] pmdomain: imx: Fix reference count leak in imx_gpc_probe()" failed to apply to 5.15-stable tree gregkh
2026-01-06 18:10 ` [PATCH 5.15.y 1/3] soc: rockchip: power-domain: Manage resource conflicts with firmware Sasha Levin
2026-01-06 18:10   ` [PATCH 5.15.y 2/3] pmdomain: Use device_get_match_data() Sasha Levin
2026-01-06 18:10   ` [PATCH 5.15.y 3/3] pmdomain: imx: Fix reference count leak in imx_gpc_probe() Sasha Levin
2026-01-06 18:43   ` Brian Norris [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=aV1XyFtvNX1lZGBE@google.com \
    --to=briannorris@chromium.org \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=pgwipeout@gmail.com \
    --cc=sashal@kernel.org \
    --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