All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frank Scheiner <frank.scheiner@web.de>
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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com, cc@epic-linux.org
Subject: Re: [PATCH 6.6 0000/1226] 6.6.145-rc2 review
Date: Thu, 23 Jul 2026 09:46:58 +0200	[thread overview]
Message-ID: <2026072333-creed-overbite-b2a9@gregkh> (raw)
In-Reply-To: <88255dcb-acac-4a74-a086-b686aaf15eca@web.de>

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].
> 
> [1]: https://github.com/linux-ia64/linux-stable-rc/actions/runs/29932232437/job/88968683064#step:8:3100
> 
> 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.
> 
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b1ddc9dfe997a5f492fa3a36487f8e7a5de30d
> 
> 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.
> 
> [3]: https://github.com/linux-ia64/linux-ia64/commit/a4085ca68e49f49f962ddff46a901ff3468574b8.patch
> 
> 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

  reply	other threads:[~2026-07-23  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:33 [PATCH 6.6 0000/1226] 6.6.145-rc2 review Greg Kroah-Hartman
2026-07-22 15:01 ` Brett A C Sheffield
2026-07-22 17:25 ` Frank Scheiner
2026-07-23  7:46   ` Greg Kroah-Hartman [this message]
2026-07-23  9:33     ` Tomáš Glozar
2026-07-23 12:21     ` Frank Scheiner
2026-07-22 18:30 ` Florian Fainelli
2026-07-22 20:11 ` Pavel Machek
2026-07-23  8:37 ` Shung-Hsi Yu
2026-07-23 10:17   ` Greg Kroah-Hartman
2026-07-23 11:28 ` Miguel Ojeda
2026-07-23 14:30 ` Wentao Guan
2026-07-23 15:54 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-07-23  9:53 Tomas Glozar

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=2026072333-creed-overbite-b2a9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=cc@epic-linux.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frank.scheiner@web.de \
    --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@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.