On Wed, Jul 22, 2026 at 07:25:26PM +0200, Frank Scheiner wrote:
On 22.07.26 16:33, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.6.145 release. There are 1226 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 Fri, 24 Jul 2026 14:31:21 +0000. Anything received after that time might be too late.
[...]
Our autobuilds for ia64 fail for 6.6.145-rc2 (actually already for -rc1 but -rc2 was released before I could respond):
drivers/cpufreq/ia64-acpi-cpufreq.c:329:27: error: initialization of 'void (*)(struct cpufreq_policy *)' from incompatible pointer type 'int (*)(struct cpufreq_policy *)' [-Wincompatible-pointer-types] 329 | .exit = acpi_cpufreq_cpu_exit, | ^~~~~~~~~~~~~~~~~~~~~ drivers/cpufreq/ia64-acpi-cpufreq.c:329:27: note: (near initialization for 'acpi_cpufreq_driver.exit')See [1].
This is due to the addition of an upstream change to drivers/cpufreq/[...]` ([2]). As this change was introduced after v6.6, it didn't change the ia64 specific driver that is still present for linux-6.6.y.
In our fork of Linux post v6.6 we carry a replay of b4b1ddc that makes the corresponding changes also for ia64. This is available on [3] (and also attached to this message) and fixes the build for me.
Can this be included for linux-6.6.y, so it continues to build for ia64 as is?
Sure, I'll queue it up. Does anyone still actually use ia64 anymore? I thought those systems were long dead.
thanks,
greg k-h