From: Brett A C Sheffield <bacs@librecast.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
Aditya Garg <gargaditya08@live.com>,
"zohar@linux.ibm.com" <zohar@linux.ibm.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"graf@amazon.com" <graf@amazon.com>,
"guoweikang.kernel@gmail.com" <guoweikang.kernel@gmail.com>,
"henry.willard@oracle.com" <henry.willard@oracle.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"jbohac@suse.cz" <jbohac@suse.cz>,
"joel.granados@kernel.org" <joel.granados@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"noodles@fb.com" <noodles@fb.com>,
"paul.x.webb@oracle.com" <paul.x.webb@oracle.com>,
"rppt@kernel.org" <rppt@kernel.org>,
"sohil.mehta@intel.com" <sohil.mehta@intel.com>,
"sourabhjain@linux.ibm.com" <sourabhjain@linux.ibm.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
"yifei.l.liu@oracle.com" <yifei.l.liu@oracle.com>
Subject: Re: [REGRESSION] Linux kernel 6.12.75 fails to compile with -Werror=implicit-function-declaration
Date: Thu, 5 Mar 2026 17:40:09 +0000 [thread overview]
Message-ID: <aam_-Y7q-c3gmfGY@auntie> (raw)
In-Reply-To: <0be301c0-f9be-4d70-9fdb-7a260ccf83ac@googlemail.com>
On 2026-03-04 20:00, Peter Schneider wrote:
> I already found and reported this in the RC cycle [1], and Sasha dropped it in -rc2 [2], and now in the release, it
> obviously has, somewhat mysteriously, reappeared [3], affecting all of today's 6.x stable branch releases.
Greg, Sasha et al.
Can we make a small adjustment to the stable kernel testing process please,
whereby we release a kernel that we have actually tested, instead of adding and
dropping patches at the last moment and releasing a kernel that no one has
tested?
We are only a small pool of testers. If we find a bug, can we fix it, release a
new RC and test again please? We can have an RC3. Even an RC4. Perhaps if we
bogoselect fewer patches in the first place we might have less work to do. It's
better to miss a backport for a bug no one has reported than to pull stuff in
without proper review.
The current stable process is introducing bugs. Bugs that never existed in
mainline.
The 3 kernels released today were tested by no one before release. The seven
kernels yesterday were similarly tested by no one before release. We weren't
given the opportunity.
There aren't enough of us to do this right, but we can do it less wrong with a
bit of caution.
Cheers,
Brett
next prev parent reply other threads:[~2026-03-05 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 17:35 [REGRESSION] Linux kernel 6.12.75 fails to compile with -Werror=implicit-function-declaration Aditya Garg
2026-03-04 17:52 ` [SEVERE] " Aditya Garg
2026-03-04 18:04 ` Aditya Garg
2026-03-04 19:00 ` Peter Schneider
2026-03-04 19:37 ` Peter Schneider
2026-03-05 17:40 ` Brett A C Sheffield [this message]
2026-03-05 20:21 ` Sasha Levin
2026-03-05 21:57 ` Brett A C Sheffield
2026-03-06 2:51 ` Sasha Levin
2026-03-05 22:06 ` Peter Schneider
2026-03-05 22:46 ` Harshit Mogalapalli
2026-03-06 0:23 ` Peter Schneider
2026-03-06 2:57 ` Sasha Levin
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=aam_-Y7q-c3gmfGY@auntie \
--to=bacs@librecast.net \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gargaditya08@live.com \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=guoweikang.kernel@gmail.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=henry.willard@oracle.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=joel.granados@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=noodles@fb.com \
--cc=paul.x.webb@oracle.com \
--cc=pschneider1968@googlemail.com \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=sohil.mehta@intel.com \
--cc=sourabhjain@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yifei.l.liu@oracle.com \
--cc=zohar@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox