public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Huacai Chen <chenhuacai@loongson.cn>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12/6.13] loongarch: Use ASM_REACHABLE
Date: Sun,  9 Mar 2025 22:14:47 -0400	[thread overview]
Message-ID: <20250309201124-5cd113a6830431fa@stable.kernel.org> (raw)
In-Reply-To: <20250308053753.3632741-1-chenhuacai@loongson.cn>

[ 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: 624bde3465f660e54a7cd4c1efc3e536349fead5

WARNING: Author mismatch between patch and upstream commit:
Backport author: Huacai Chen<chenhuacai@loongson.cn>
Commit author: Peter Zijlstra<peterz@infradead.org>

Status in newer kernel trees:
6.13.y | Present (different SHA1: 92a3a4ad5be7)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  624bde3465f66 ! 1:  0911995aac2a8 loongarch: Use ASM_REACHABLE
    @@ Metadata
      ## Commit message ##
         loongarch: Use ASM_REACHABLE
     
    +    commit 624bde3465f660e54a7cd4c1efc3e536349fead5 upstream.
    +
         annotate_reachable() is unreliable since the compiler is free to place
         random code inbetween two consecutive asm() statements.
     
         This removes the last and only annotate_reachable() user.
     
    +    Backport to solve a build error since relevant commits have already been
    +    backported.
    +
         Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
         Acked-by: Josh Poimboeuf <jpoimboe@kernel.org>
         Link: https://lore.kernel.org/r/20241128094312.133437051@infradead.org
    +    Closes: https://lore.kernel.org/loongarch/20250307214943.372210-1-ojeda@kernel.org/
    +    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
     
      ## arch/loongarch/include/asm/bug.h ##
     @@
---

Results of testing on various branches:

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

      parent reply	other threads:[~2025-03-10  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08  5:37 [PATCH 6.12/6.13] loongarch: Use ASM_REACHABLE Huacai Chen
2025-03-09 19:56 ` Miguel Ojeda
2025-03-10  2:14 ` 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=20250309201124-5cd113a6830431fa@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --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