From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Borislav Petkov <bp@alien8.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@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
nik.borisov@suse.com, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 6.6 000/147] 6.6.81-rc2 review
Date: Thu, 6 Mar 2025 18:59:30 +0100 [thread overview]
Message-ID: <2025030604-bootie-sandbox-3fcd@gregkh> (raw)
In-Reply-To: <CA+G9fYtfmMThUC+erk6jVk8BN0jWJCw=FnKh68ypwhgv65OZ+w@mail.gmail.com>
On Thu, Mar 06, 2025 at 10:59:35PM +0530, Naresh Kamboju wrote:
> On Thu, 6 Mar 2025 at 20:50, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.6.81 release.
> > There are 147 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, 08 Mar 2025 15:13:38 +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.81-rc2.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
>
>
> Regressions on i386 the defconfig builds failed with clang-20
> and gcc-13 the stable-rc 6.6.81-rc2.
>
> First seen on the
> Good: v6.6.78
> Bad: v6.6.78-442-g8f0527d547fe
>
> * i386 build
> - clang-20-defconfig
> - clang-nightly-defconfig
> - gcc-13-defconfig
> - gcc-8-defconfig
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
>
> Build regression: i386 microcode core.c use of undeclared identifier
> 'initrd_start_early'
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
> arch/x86/kernel/cpu/microcode/core.c:198:11: error: use of undeclared
> identifier 'initrd_start_early'; did you mean 'initrd_start'?
> 198 | start = initrd_start_early;
> | ^~~~~~~~~~~~~~~~~~
> | initrd_start
> include/linux/initrd.h:18:22: note: 'initrd_start' declared here
> 18 | extern unsigned long initrd_start, initrd_end;
> | ^
> 1 error generated.
Boris, this is due to your 6.6 backports, did you happen to test-build
i386?
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-06 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 15:20 [PATCH 6.6 000/147] 6.6.81-rc2 review Greg Kroah-Hartman
2025-03-06 17:16 ` Pavel Machek
2025-03-06 17:29 ` Naresh Kamboju
2025-03-06 17:44 ` Borislav Petkov
2025-03-06 18:01 ` Greg Kroah-Hartman
2025-03-08 20:17 ` Borislav Petkov
2025-03-09 8:36 ` Greg Kroah-Hartman
2025-03-06 17:59 ` Greg Kroah-Hartman [this message]
2025-03-06 18:04 ` Florian Fainelli
2025-03-06 18:10 ` Mark Brown
2025-03-07 2:43 ` Peter Schneider
2025-03-07 9:47 ` Jon Hunter
2025-03-07 19:20 ` Hardik Garg
2025-03-08 15:24 ` Guenter Roeck
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=2025030604-bootie-sandbox-3fcd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--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=naresh.kamboju@linaro.org \
--cc=nik.borisov@suse.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox