From: "BillXiang" <xiangwencheng@lanxincomputing.com>
To: "Paul Walmsley" <pjw@kernel.org>,
"Andrew Jones" <ajones@ventanamicro.com>
Cc: <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] riscv: Move user-visible sbi ext ids to uapi
Date: Thu, 9 Oct 2025 15:27:18 +0800 [thread overview]
Message-ID: <abf80762-79ab-49ae-98ef-9a632cbad151@lanxincomputing.com> (raw)
In-Reply-To: <d9720a12-5efc-1be6-b4a7-7a8888b959a0@kernel.org>
On 10/9/2025 4:37 AM, Paul Walmsley wrote:
> Hi Drew,
>
> On Wed, 8 Oct 2025, Andrew Jones wrote:
>
>> On Wed, Oct 08, 2025 at 12:17:01PM -0600, Paul Walmsley wrote:
>> ...
>>> I do have some broader questions: is this patch really needed? Is it
>>> fixing anything that's broken? These SBI constants aren't defined by the
>>> kernel; they come from RISC-V standards.
Hi All,
Thanks for the review, and sorry for the noise my earlier mistake caused.
Just to clarify the intent of this patch: these SBI constants are
defined by the RISC-V spec, but they are implemented by kernel.
IMO, for a userspace developer working on linux it's better to include
this constants from kernel instead of define them again.
If you don't like the patch, feel free to ignore it, nothing breaks
either way.
Additionally, the goodness of UAPI was described in[1].
[1] https://lwn.net/Articles/507794/
>>
>> Hi Paul,
>>
>> You're right that we don't want this patch. I hadn't noticed that the same
>> patch was posted more than once or I would have nacked it here too. I
>> replied to the other posting[1] a couple weeks ago.
>>
>> [1] https://lore.kernel.org/all/20250924-7e9764acec6722b5ef29ce7d@orel/
>
> Thanks for the heads up and for the early review. Patchwork didn't pick
> up the thread for whatever reason beyond the initial patch, and I didn't
> bother to check the mail archive...
>
>
> - Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-10-09 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 9:21 [PATCH] riscv: Move user-visible sbi ext ids to uapi BillXiang
2025-10-08 18:17 ` Paul Walmsley
2025-10-08 20:06 ` Andrew Jones
2025-10-08 20:37 ` Paul Walmsley
2025-10-09 7:27 ` BillXiang [this message]
2025-10-09 15:07 ` Andrew Jones
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=abf80762-79ab-49ae-98ef-9a632cbad151@lanxincomputing.com \
--to=xiangwencheng@lanxincomputing.com \
--cc=ajones@ventanamicro.com \
--cc=linux-riscv@lists.infradead.org \
--cc=pjw@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