From: Nathan Chancellor <nathan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, llvm@lists.linux.dev
Subject: Backports for 6.1 and older due to clang -Qunused-arguments change
Date: Wed, 4 Jun 2025 16:31:41 -0700 [thread overview]
Message-ID: <20250604233141.GA2374479@ax162> (raw)
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Hi Greg and Sasha,
Please find attached backports for commit feb843a469fb ("kbuild: add
$(CLANG_FLAGS) to KBUILD_CPPFLAGS") and its dependent changes, commit
d5c8d6e0fa61 ("kbuild: Update assembler calls to use proper flags and
language target") and its dependent changes, and commit 7db038d9790e
("drm/amd/display: Do not add '-mhard-float' to dml_ccflags for clang")
for 6.1 and earlier. The second listed change is already in 6.1 so that
series is a little shorter.
These changes are needed there due to an upstream LLVM change [1] that
changes the behavior of -Qunused-arguments with unknown target options,
which is only used in 6.1 and older since I removed it in commit
8d9acfce3332 ("kbuild: Stop using '-Qunused-arguments' with clang") in
6.3.
Please let me know if there are any issues, I will try to pay attention
for any issues that crop up in the stable review period from these
changes but please ping me if you remember.
Cheers,
Nathan
[1]: https://github.com/llvm/llvm-project/commit/a4b2f4a72aa9b4655ecc723838830e0a7f29c9ca
[-- Attachment #2: 5.4-llvm-qunused-arguments-change.mbox --]
[-- Type: application/mbox, Size: 20064 bytes --]
[-- Attachment #3: 5.10-llvm-qunused-arguments-change.mbox --]
[-- Type: application/mbox, Size: 23747 bytes --]
[-- Attachment #4: 5.15-llvm-qunused-arguments-change.mbox --]
[-- Type: application/mbox, Size: 23928 bytes --]
[-- Attachment #5: 6.1-llvm-qunused-arguments-change.mbox --]
[-- Type: application/mbox, Size: 10440 bytes --]
reply other threads:[~2025-06-04 23:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250604233141.GA2374479@ax162 \
--to=nathan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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