From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org
Subject: Re: [PATCH 5.4 000/403] 5.4.297-rc1 review
Date: Wed, 27 Aug 2025 09:36:24 +0200 [thread overview]
Message-ID: <2025082705-ascent-parted-b05d@gregkh> (raw)
In-Reply-To: <ed898a83-48d1-4cce-87b4-b67ee4fdc047@nvidia.com>
On Tue, Aug 26, 2025 at 03:46:37PM +0100, Jon Hunter wrote:
> Hi Greg,
>
> On 26/08/2025 12:05, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.297 release.
> > There are 403 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 28 Aug 2025 11:08:17 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.297-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
> > -------------
> > Pseudo-Shortlog of commits:
>
> ...
> > Prashant Malani <pmalani@google.com>
> > cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag
>
>
> The above commit is causing the following build failure ...
>
> drivers/cpufreq/cppc_cpufreq.c:410:40: error: ‘CPUFREQ_NEED_UPDATE_LIMITS’ undeclared here (not in a function)
> 410 | .flags = CPUFREQ_CONST_LOOPS | CPUFREQ_NEED_UPDATE_LIMITS,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> make[2]: *** [scripts/Makefile.build:262: drivers/cpufreq/cppc_cpufreq.o] Error 1
>
>
> This is seen with ARM64 but I am guessing will be seen for
> other targets too.
Thanks, somehow this missed my build tests. I've dropped it from the
tree now and will push out a -rc2.
greg k-h
next prev parent reply other threads:[~2025-08-27 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 11:05 [PATCH 5.4 000/403] 5.4.297-rc1 review Greg Kroah-Hartman
2025-08-26 11:10 ` [PATCH 5.4 313/403] move_mount: allow to add a mount into an existing group Greg Kroah-Hartman
2025-08-26 14:46 ` [PATCH 5.4 000/403] 5.4.297-rc1 review Jon Hunter
2025-08-27 7:36 ` Greg Kroah-Hartman [this message]
2025-08-27 9:19 ` Anders Roxell
2025-08-27 10:15 ` Greg Kroah-Hartman
2025-08-26 17:01 ` Florian Fainelli
2025-08-26 18:31 ` Brett A C Sheffield
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=2025082705-ascent-parted-b05d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).