From: Paul Walmsley <pjw@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: bug: Make RV32 use GENERIC_BUG_RELATIVE_POINTERS
Date: Thu, 20 Aug 2026 20:28:42 -0600 (MDT) [thread overview]
Message-ID: <a34a939f-1a6b-8e24-d7af-39e38d6abfd7@kernel.org> (raw)
In-Reply-To: <20260221024255.3552-1-jszhang@kernel.org>
On Sat, 21 Feb 2026, Jisheng Zhang wrote:
> x86 did this in commit b0a848f4a47a ("x86/bugs: Make i386 use
> GENERIC_BUG_RELATIVE_POINTERS")
>
> powerpc did this in commit 1baa1f70ef77 ("powerpc: Allow relative
> pointers in bug table entries")
>
> Similar as x86 and powerpc does, make RV32 use
> GENERIC_BUG_RELATIVE_POINTERS for "there is only one code path." and
> "less #ifdef is more better".
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
Thanks, queued for v7.3-rc.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: bug: Make RV32 use GENERIC_BUG_RELATIVE_POINTERS
Date: Thu, 20 Aug 2026 20:28:42 -0600 (MDT) [thread overview]
Message-ID: <a34a939f-1a6b-8e24-d7af-39e38d6abfd7@kernel.org> (raw)
In-Reply-To: <20260221024255.3552-1-jszhang@kernel.org>
On Sat, 21 Feb 2026, Jisheng Zhang wrote:
> x86 did this in commit b0a848f4a47a ("x86/bugs: Make i386 use
> GENERIC_BUG_RELATIVE_POINTERS")
>
> powerpc did this in commit 1baa1f70ef77 ("powerpc: Allow relative
> pointers in bug table entries")
>
> Similar as x86 and powerpc does, make RV32 use
> GENERIC_BUG_RELATIVE_POINTERS for "there is only one code path." and
> "less #ifdef is more better".
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
Thanks, queued for v7.3-rc.
- Paul
next prev parent reply other threads:[~2026-08-21 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 2:42 [PATCH] riscv: bug: Make RV32 use GENERIC_BUG_RELATIVE_POINTERS Jisheng Zhang
2026-02-21 2:42 ` Jisheng Zhang
2026-08-21 2:28 ` Paul Walmsley [this message]
2026-08-21 2:28 ` Paul Walmsley
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=a34a939f-1a6b-8e24-d7af-39e38d6abfd7@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
/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.