On Wed, Aug 27, 2025 at 11:19:11AM +0200, Anders Roxell wrote:
On Wed, 27 Aug 2025 at 09:36, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
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... 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.
[for the record]
We also see the following build regression on ARM64 with gcc-12 and clang-20.
Validation is in progress for RC2.
Build Regression: 5.4.297-rc1 arm64 use of undeclared identifier CPUFREQ_NEED_UPDATE_LIMITS
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Should be fixed in -rc2, right?