All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Paul Walmsley <pjw@kernel.org>
Cc: BillXiang <xiangwencheng@lanxincomputing.com>,
	 linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: Move user-visible sbi ext ids to uapi
Date: Wed, 8 Oct 2025 15:06:36 -0500	[thread overview]
Message-ID: <20251008-a966ea0e3d8bb6dbd85f6c6a@orel> (raw)
In-Reply-To: <3bd01b1c-07e1-c545-8256-f83e3343247e@kernel.org>

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 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,
drew

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-10-08 20:06 UTC|newest]

Thread overview: 16+ 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 [this message]
2025-10-08 20:37     ` Paul Walmsley
2025-10-09  7:27       ` BillXiang
2025-10-09 15:07         ` Andrew Jones
  -- strict thread matches above, loose matches on Subject: below --
2025-09-17  8:52 BillXiang
2025-09-17  8:52 ` BillXiang
2025-09-23 20:14 ` Andrew Jones
2025-09-23 20:14   ` Andrew Jones
2025-09-24  2:35   ` BillXiang
2025-09-24  2:35     ` BillXiang
2025-09-24 12:54     ` Andrew Jones
2025-09-24 12:54       ` Andrew Jones
2025-09-25  2:09       ` BillXiang
2025-09-25  2:09         ` BillXiang

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=20251008-a966ea0e3d8bb6dbd85f6c6a@orel \
    --to=ajones@ventanamicro.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=pjw@kernel.org \
    --cc=xiangwencheng@lanxincomputing.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.