Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hal Feng <hal.feng@starfivetech.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree
Date: Mon, 29 Dec 2025 16:36:26 +0100	[thread overview]
Message-ID: <2025122908-skinning-mortuary-89c7@gregkh> (raw)
In-Reply-To: <ZQ2PR01MB1307AE907F8899DA89F1085CE6B42@ZQ2PR01MB1307.CHNPR01.prod.partner.outlook.cn>

On Mon, Dec 22, 2025 at 01:54:03AM +0000, Hal Feng wrote:
> > On 19.12.25 20:31, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     cpufreq: dt-platdev: Add JH7110S SOC to the allowlist
> > 
> > to the 6.18-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-
> > queue.git;a=summary
> > 
> > The filename of the patch is:
> >      cpufreq-dt-platdev-add-jh7110s-soc-to-the-allowlist.patch
> > and it can be found in the queue-6.18 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree, please let
> > <stable@vger.kernel.org> know about it.
> 
> As series [1] is accepted, this patch will be not needed and will be reverted in the mainline.
> 
> [1] https://lore.kernel.org/all/20251212211934.135602-1-e@freeshell.de/
> 
> So we should not add it to the stable tree. Thanks.

Why can't we take the commit that also landed in mainline for this too?
What is that git id?

thanks,

greg k-h

  reply	other threads:[~2025-12-29 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251219123039.977903-1-sashal@kernel.org>
2025-12-22  1:54 ` Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree Hal Feng
2025-12-29 15:36   ` Greg KH [this message]
2026-01-04  6:25     ` Hal Feng
2026-01-08  9:20       ` Greg KH

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=2025122908-skinning-mortuary-89c7@gregkh \
    --to=greg@kroah.com \
    --cc=hal.feng@starfivetech.com \
    --cc=rafael@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=viresh.kumar@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