From: Sasha Levin <sashal@kernel.org>
To: kernelci-results@groups.io
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, KernelCI bot <bot@kernelci.org>
Subject: Re: [REGRESSION] stable-rc/linux-6.6.y: (build) incompatible function pointer types initializing 'void (*)(struct ...
Date: Wed, 22 Jul 2026 12:43:11 -0400 [thread overview]
Message-ID: <20260722113501.rc-reply-0001@kernel.org> (raw)
In-Reply-To: <178467474625.1334.6331115540835663024@kernelci.org>
On Tue, Jul 21, 2026 at 10:59:07PM -0000, KernelCI bot wrote:
> New build issue found on stable-rc/linux-6.6.y:
>
> drivers/cpufreq/cpufreq-nforce2.c:376:10: error: incompatible function pointer types initializing 'void (*)(struct cpufreq_policy *)' with an expression of type 'int (struct cpufreq_policy *)' [-Wincompatible-function-pointer-types]
This was caused by an incomplete backport of b4b1ddc9dfe9 ("cpufreq:
Make cpufreq_driver::exit() return void"): 6.6 still has drivers
(nforce2, loongson2, ia64-acpi-cpufreq) whose int-returning exit()
callbacks were removed upstream by prerequisite commits that were
never queued.
Dropped the offending patch from the 6.6 queue along with its
dependencies:
- "cpufreq: pcc: Remove empty exit() callback"
- "cpufreq: qcom-cpufreq-hw: Fix possible double free" (will be
requeued separately as a context-adjusted backport)
Thanks for the report.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-22 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 22:59 [REGRESSION] stable-rc/linux-6.6.y: (build) incompatible function pointer types initializing 'void (*)(struct KernelCI bot
2026-07-22 16:43 ` Sasha Levin [this message]
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=20260722113501.rc-reply-0001@kernel.org \
--to=sashal@kernel.org \
--cc=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=stable@vger.kernel.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.