From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sergio González Collado" <sergio.collado@gmail.com>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH v2 6.1.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c
Date: Wed, 25 Jun 2025 10:07:22 -0400 [thread overview]
Message-ID: <20250624212637-996f16e3b55b968c@stable.kernel.org> (raw)
In-Reply-To: <20250624165852.7689-3-sergio.collado@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: f710202b2a45addea3dcdcd862770ecbaf6597ef
WARNING: Author mismatch between patch and upstream commit:
Backport author: <sergio.collado@gmail.com>
Commit author: Nathan Chancellor<nathan@kernel.org>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (different SHA1: ebd352672790)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: f710202b2a45a ! 1: 29c4ece87594a x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c
@@ Metadata
## Commit message ##
x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c
+ commit f710202b2a45addea3dcdcd862770ecbaf6597ef upstream.
+
After commit c104c16073b7 ("Kunit to check the longest symbol length"),
there is a warning when building with clang because there is now a
definition of unlikely from compiler.h in tools/include/linux, which
@@ Commit message
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
+ Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
Link: https://lore.kernel.org/r/20250318-x86-decoder-test-fix-unlikely-redef-v1-1-74c84a7bf05b@kernel.org
## arch/x86/tools/insn_decoder_test.c ##
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-06-25 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 16:58 [PATCH v2 6.1.y 0/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-24 16:58 ` [PATCH v2 6.1.y 1/2] " Sergio González Collado
2025-06-25 14:07 ` Sasha Levin
2025-06-24 16:58 ` [PATCH v2 6.1.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c Sergio González Collado
2025-06-25 14:07 ` Sasha Levin [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=20250624212637-996f16e3b55b968c@stable.kernel.org \
--to=sashal@kernel.org \
--cc=sergio.collado@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).