From: Nathan Chancellor <nathan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
achill@achill.org, Madhavan Srinivasan <maddy@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
clang-built-linux <llvm@lists.linux.dev>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Ben Copeland <benjamin.copeland@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 5.4 00/23] 5.4.298-rc1 review
Date: Wed, 3 Sep 2025 10:28:59 -0700 [thread overview]
Message-ID: <20250903172859.GB3288670@ax162> (raw)
In-Reply-To: <2025090317-envelope-professed-b38a@gregkh>
On Wed, Sep 03, 2025 at 11:48:11AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 03, 2025 at 03:11:26PM +0530, Naresh Kamboju wrote:
> > Build regression: stable-rc 5.4.298-rc1 powerpc/boot/util.S:44: Error:
> > junk at end of line, first unrecognized character is `0'
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Known issue, patch already submitted:
> https://lore.kernel.org/r/20250902235234.2046667-1-nathan@kernel.org
>
> Will queue that up for the next round of releases, using clang-20 on
> 5.4.y is brave :)
Just for the record, there is nothing clang specific here, it is a
binutils problem. The clang-20 TuxMake containers just happen to have a
newer copy of binutils from Debian Trixie after [1]. I would expect one
of the updated GCC versions to reproduce the same issue, unless they
don't build 5.4 for other reasons. I always try to ensure every stable
version builds with latest clang so I would not consider it that brave
:)
I plan to send a v2 addressing Segher's comments later today.
[1]: https://gitlab.com/Linaro/tuxmake/-/commit/46280e20b8ed2df749e9115640271c0a6a2c812c
Cheers,
Nathan
next prev parent reply other threads:[~2025-09-03 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 13:21 [PATCH 5.4 00/23] 5.4.298-rc1 review Greg Kroah-Hartman
2025-09-02 16:32 ` Brett A C Sheffield
2025-09-02 17:10 ` [PATCH 5.4 00/23] " Florian Fainelli
2025-09-02 18:03 ` Jon Hunter
2025-09-03 9:41 ` Naresh Kamboju
2025-09-03 9:48 ` Greg Kroah-Hartman
2025-09-03 17:28 ` Nathan Chancellor [this message]
2025-09-03 18:49 ` [External] : " ALOK TIWARI
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=20250903172859.GB3288670@ax162 \
--to=nathan@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.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=llvm@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--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 \
--cc=venkat88@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