From: Miguel Ojeda <ojeda@kernel.org>
To: chenhuacai@loongson.cn
Cc: chenhuacai@kernel.org, gregkh@linuxfoundation.org,
jpoimboe@kernel.org, kernel@xen0n.name,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
peterz@infradead.org, sashal@kernel.org, stable@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.12/6.13] loongarch: Use ASM_REACHABLE
Date: Sun, 9 Mar 2025 20:56:22 +0100 [thread overview]
Message-ID: <20250309195622.1541936-1-ojeda@kernel.org> (raw)
In-Reply-To: <20250308053753.3632741-1-chenhuacai@loongson.cn>
On Sat, 08 Mar 2025 13:37:53 +0800 Huacai Chen <chenhuacai@loongson.cn> wrote:
>
> From: Peter Zijlstra <peterz@infradead.org>
>
> 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>
This indeed removes the build failure for me -- built-tested for loongarch64
(together with the rest of the Rust long backport series):
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-03-09 19:56 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 [this message]
2025-03-10 2:14 ` Sasha Levin
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=20250309195622.1541936-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=peterz@infradead.org \
--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 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.