From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
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
Subject: Re: [PATCH 6.6 000/204] 6.6.89-rc1 review
Date: Thu, 1 May 2025 09:54:41 +0200 [thread overview]
Message-ID: <2025050148-expand-definite-8401@gregkh> (raw)
In-Reply-To: <44f876a3-7229-4320-8715-e49a122aa2ea@w6rz.net>
On Wed, Apr 30, 2025 at 05:27:31PM -0700, Ron Economos wrote:
> On 4/30/25 10:59, Naresh Kamboju wrote:
> > On Tue, 29 Apr 2025 at 23:41, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > > This is the start of the stable review cycle for the 6.6.89 release.
> > > There are 204 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 Thu, 01 May 2025 16:10:15 +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.89-rc1.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
> >
> > Following two build regressions found one on riscv and s390.
> >
> > 1)
> > Regressions on riscv build with allyesconfig and allmodconfig with toolchains
> > gcc-13 and clang-20 failed on stable-rc 6.6.89-rc1.
> >
> > * riscv, build
> > - clang-20-allmodconfig
> > - gcc-13-allmodconfig
> > - gcc-13-allyesconfig
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducibility? Yes
> >
> > Build regression: riscv uprobes.c error unused variable 'start'
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > ## Build error riscv
> > arch/riscv/kernel/probes/uprobes.c: In function 'arch_uprobe_copy_ixol':
> > arch/riscv/kernel/probes/uprobes.c:170:23: error: unused variable
> > 'start' [-Werror=unused-variable]
> > 170 | unsigned long start = (unsigned long)dst;
> > | ^~~~~
> > cc1: all warnings being treated as errors
>
> This warning is caused by not having the fixup patch "riscv: Replace
> function-like macro by static inline function" upstream commit
> 121f34341d396b666d8a90b24768b40e08ca0d61 in 6.6.89-rc1, 6.1.136-rc1 and
> 5.15.181-rc1. Looks like it didn't apply cleanly to those versions.
>
> The fixup patch was included in 6.14.5-rc1 and 6.12.26-rc1.
Thanks, I'll go drop this from 5.15.y, 6.1.y, and 6.6.y for now and wait
for some fixes to be resent.
greg k-h
next prev parent reply other threads:[~2025-05-01 7:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 16:41 Greg Kroah-Hartman
2025-04-30 1:10 ` Peter Schneider
2025-04-30 7:44 ` Hardik Garg
2025-04-30 15:04 ` Jon Hunter
2025-05-01 7:27 ` Jon Hunter
2025-05-01 7:47 ` Greg Kroah-Hartman
2025-04-30 15:54 ` Miguel Ojeda
2025-04-30 15:58 ` Shuah Khan
2025-04-30 17:59 ` Naresh Kamboju
2025-05-01 0:27 ` Ron Economos
2025-05-01 7:54 ` Greg Kroah-Hartman [this message]
2025-04-30 21:15 ` Ron Economos
2025-04-30 22:48 ` Mark Brown
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=2025050148-expand-definite-8401@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.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=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=re@w6rz.net \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®