RE: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree

RE: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree

[Hal Feng]

> 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.

Best regards,
Hal

> 
> 
> 
> commit f922a9b37397e7db449e3fa61c33c542ad783f87
> Author: Hal Feng <hal.feng@starfivetech.com>
> Date:   Thu Oct 16 16:00:48 2025 +0800
> 
>     cpufreq: dt-platdev: Add JH7110S SOC to the allowlist
> 
>     [ Upstream commit 6e7970cab51d01b8f7c56f120486c571c22e1b80 ]
> 
>     Add the compatible strings for supporting the generic
>     cpufreq driver on the StarFive JH7110S SoC.
> 
>     Signed-off-by: Hal Feng <hal.feng@starfivetech.com>
>     Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
>     Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>     Signed-off-by: Sasha Levin <sashal@kernel.org>
> 
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-
> dt-platdev.c
> index cd1816a12bb99..dc11b62399ad5 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -87,6 +87,7 @@ static const struct of_device_id allowlist[] __initconst = {
>  	{ .compatible = "st-ericsson,u9540", },
> 
>  	{ .compatible = "starfive,jh7110", },
> +	{ .compatible = "starfive,jh7110s", },
> 
>  	{ .compatible = "ti,omap2", },
>  	{ .compatible = "ti,omap4", },

Re: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree

[Greg KH]

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

RE: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree

[Hal Feng]

> On 29.12.25 23:36, Greg KH wrote:
> 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?

Those commits are applied to the riscv-dt-for-next branch [1], but not landed in the mainline yet.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=riscv-dt-for-next

The commit IDs in riscv-dt-for-next branch are
d2091990c5c1
7c9a5fd6bb19
4297ddbf1d14

Best regards,
Hal

Re: Patch "cpufreq: dt-platdev: Add JH7110S SOC to the allowlist" has been added to the 6.18-stable tree

[Greg KH]

On Sun, Jan 04, 2026 at 06:25:56AM +0000, Hal Feng wrote:
> > On 29.12.25 23:36, Greg KH wrote:
> > 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?
> 
> Those commits are applied to the riscv-dt-for-next branch [1], but not landed in the mainline yet.
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=riscv-dt-for-next
> 
> The commit IDs in riscv-dt-for-next branch are
> d2091990c5c1
> 7c9a5fd6bb19
> 4297ddbf1d14

Great, when they hit Linus's tree, please let us know and we can queue
them up then.

thanks,

greg k-h