Re: [PATCH 6.6 000/484] 6.6.148-rc1 review

[Frank Scheiner <frank.scheiner@web.de>]

On 30.07.26 16:08, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.148 release.
> There are 484 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 Sat, 01 Aug 2026 14:13:41 +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/v6.x/stable-review/patch-6.6.148-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-6.6.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

I didn't notice earlier, but we now seem to have a mirrored version of
the build problem described for 6.6.145-rc2 ([1]) earlier:

from: https://github.com/linux-ia64/linux-stable-rc/actions/runs/30608172560/job/91087240301#step:8:3099
```
drivers/cpufreq/ia64-acpi-cpufreq.c:327:27: error: initialization of 'int (*)(struct cpufreq_policy *)' from incompatible pointer type 'void (*)(struct cpufreq_policy *)' [-Wincompatible-pointer-types]
  327 |         .exit           = acpi_cpufreq_cpu_exit,
      |                           ^~~~~~~~~~~~~~~~~~~~~
drivers/cpufreq/ia64-acpi-cpufreq.c:327:27: note: (near initialization for 'acpi_cpufreq_driver.exit')
make[6]: *** [scripts/Makefile.build:243: drivers/cpufreq/ia64-acpi-cpufreq.o] Error 1
make[5]: *** [scripts/Makefile.build:480: drivers/cpufreq] Error 2
make[5]: *** Waiting for unfinished jobs....
```

[1]: https://lore.kernel.org/stable/88255dcb-acac-4a74-a086-b686aaf15eca@web.de/

Looking into the released 6.6.145 ([2]) the patch "cpufreq: Make
cpufreq_driver->exit() return void" ([3]) that created the original
problem for the ia64 buld in 6.6.145-rc1 and -rc2 was gone in the
released 6.6.145.

[2]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=01f5e56c58488ddef1a0a7bc2102bab9cf0031f9

[3]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b1ddc9dfe997a5f492fa3a36487f8e7a5de30d

Hence the patch which replays that change also for ia64 needs to go now,
too.

Short of an upstream commit for this patch, I can only point you to the
patch in:

* linux-stable-rc:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-6.6.y&id=bb51b626b5a8ef349b11876572540f19ad4d5030

* stable:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=bb51b626b5a8ef349b11876572540f19ad4d5030

* stable-queue:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=8b7e20cd309ee12f5916f0fa96569fcd0484551f

..., you decide what you prefer. HTH.

Cheers,
Frank

P.S.
Would the patch from us have been dropped automatically with [3] if ours
had contained a `Fixes: b4b1ddc9dfe997a5f492fa3a36487f8e7a5de30d
("cpufreq: Make cpufreq_driver->exit() return void")` tag maybe?