All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, sergio.collado@gmail.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c
Date: Sun,  8 Jun 2025 22:34:49 -0400	[thread overview]
Message-ID: <20250608131945-4e96cd203d765c70@stable.kernel.org> (raw)
In-Reply-To: <20250608145450.7024-3-sergio.collado@gmail.com>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
ℹ️ This is part 2/2 of a series
⚠️ Found matching upstream commit but patch is missing proper reference to it

Found matching upstream commit: f710202b2a45addea3dcdcd862770ecbaf6597ef

WARNING: Author mismatch between patch and found 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.14.y | Not found

Note: The patch differs from the upstream commit:
---
1:  f710202b2a45a ! 1:  aea5c55c49b88 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
     
    +    From Nathan Chancellor <nathan@kernel.org>
    +
    +    [Upstream f710202b2a45addea3dcdcd862770ecbaf6597ef]
    +
         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: Ingo Molnar <mingo@kernel.org>
         Acked-by: Shuah Khan <skhan@linuxfoundation.org>
         Link: https://lore.kernel.org/r/20250318-x86-decoder-test-fix-unlikely-redef-v1-1-74c84a7bf05b@kernel.org
    +    Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
     
      ## arch/x86/tools/insn_decoder_test.c ##
     @@
---

NOTE: These results are for this patch alone. Full series testing will be
performed when all parts are received.

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y       |  Success    |  Success   |

  parent reply	other threads:[~2025-06-09  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-08 14:54 [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-08 14:54 ` [PATCH 6.12.y 1/2] " Sergio González Collado
2025-06-08 15:59   ` Miguel Ojeda
2025-06-08 16:10     ` Sergio González Collado
2025-06-17 14:00       ` Greg KH
2025-06-17 15:50         ` Sergio González Collado
2025-06-17 16:04           ` Miguel Ojeda
2025-06-09  2:34   ` Sasha Levin
2025-06-08 14:54 ` [PATCH 6.12.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c Sergio González Collado
2025-06-08 16:00   ` Miguel Ojeda
2025-06-09  2:34   ` Sasha Levin [this message]
2025-06-08 15:59 ` [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Miguel Ojeda

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=20250608131945-4e96cd203d765c70@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.