From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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
Subject: Re: [PATCH 6.6 000/676] 6.6.64-rc1 review
Date: Sat, 7 Dec 2024 19:47:36 -0700 [thread overview]
Message-ID: <20241208024736.GA2495976@ax162> (raw)
In-Reply-To: <CA+G9fYtsYhXwhewSJUnGAwFmSa5AnOvuREZiOGRCsOUWb6Kx3Q@mail.gmail.com>
On Sun, Dec 08, 2024 at 01:20:19AM +0530, Naresh Kamboju wrote:
> NOTE:
> [Not a kernel regressions]
> Powerpc clang nightly defconfig builds are failing on stable-rc linux-6.6.y
> clang: error: invalid value 'r13' in 'mstack-protector-guard-reg=',
> expected one of: r2
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2pqeSKGTShWpi3PB2dFTogUwhpJ/
It is a kernel regression, it is fixed by taking
https://lore.kernel.org/stable/20241206220926.2099603-1-nathan@kernel.org/
atomically with the other powerpc stack protector clang fixes in this
series, which matches upstream.
Cheers,
Nathan
next prev parent reply other threads:[~2024-12-08 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 14:26 [PATCH 6.6 000/676] 6.6.64-rc1 review Greg Kroah-Hartman
2024-12-06 14:33 ` [PATCH 6.6 371/676] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-06 18:27 ` [PATCH 6.6 000/676] 6.6.64-rc1 review Mark Brown
2024-12-06 22:44 ` Florian Fainelli
2024-12-07 1:48 ` Peter Schneider
2024-12-07 7:53 ` Ron Economos
2024-12-07 9:04 ` Muhammad Usama Anjum
2024-12-07 19:50 ` Naresh Kamboju
2024-12-08 2:47 ` Nathan Chancellor [this message]
2024-12-07 22:32 ` Miguel Ojeda
2024-12-08 16:53 ` Harshit Mogalapalli
2024-12-10 10:01 ` Guenter Roeck
2024-12-11 15:05 ` Greg Kroah-Hartman
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=20241208024736.GA2495976@ax162 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=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