From: Greg KH <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: sashal@kernel.org, ndesaulniers@google.com,
naresh.kamboju@linaro.org, stable@vger.kernel.org,
llvm@lists.linux.dev, "Masahiro Yamada" <masahiroy@kernel.org>,
"Linux Kernel Functional Testing" <lkft@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
tsbogend@alpha.franken.de, linux-mips@vger.kernel.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 6.1 0/4] Update as-{instr,option} to use KBUILD_AFLAGS
Date: Mon, 19 Jun 2023 09:51:44 +0200 [thread overview]
Message-ID: <2023061934-scuttle-unveiled-1801@gregkh> (raw)
In-Reply-To: <20230612-6-1-asssembler-target-llvm-17-v1-0-75605d553401@kernel.org>
On Wed, Jun 14, 2023 at 11:04:34AM -0700, Nathan Chancellor wrote:
> Hi all,
>
> This series backports commit d5c8d6e0fa61 ("kbuild: Update assembler
> calls to use proper flags and language target") to linux-6.1.y to
> address a recent issue caused by a change in behavior in clang:
>
> https://lore.kernel.org/CA+G9fYsJq0sPC+q6vLNKUgBqCGmmjDrfeP4R1-95Eu28FJRY_A@mail.gmail.com/
> https://lore.kernel.org/20230612185424.GA2891387@dev-arch.thelio-3990X/
>
> While that was not the original intention of the aforementioned change,
> it ends up resolving the issue for the same reason, by not passing flags
> that are not supported or necessary for the current language target
> (KBUILD_CFLAGS for .c files and KBUILD_AFLAGS for .S files) when testing
> flags for that language target.
>
> All patches except the second one are direct backports from mainline.
> The second patch is a stable specific patch because the upstream
> solution could break stable due to the minimum supported version of
> binutils in mainline being a newer version than 6.1 and earlier; it
> chooses to do the more conservative fix, which was alluded to in the
> changelog of the upstream commit.
>
> For now, this is just a 6.1 issue. If the issue occurs in older
> releases, I will send separate backports. If there are any issues or
> objections to this series, please let me know.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-06-19 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 18:04 [PATCH 6.1 0/4] Update as-{instr,option} to use KBUILD_AFLAGS Nathan Chancellor
2023-06-14 18:04 ` [PATCH 6.1 2/4] MIPS: Move '-Wa,-msoft-float' check from as-option to cc-option Nathan Chancellor
2023-06-19 7:51 ` Greg KH [this message]
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=2023061934-scuttle-unveiled-1801@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anders.roxell@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=philmd@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).