From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
jszhang@kernel.org, andrew.jones@linux.dev,
thecharlesjenkins@gmail.com, guodong.xu@oss.qualcomm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] riscv: remove RISCV_ISA_EXT_BUNDLE[_VALIDATE]
Date: Wed, 18 Nov 2026 03:40:06 +0000 [thread overview]
Message-ID: <179497320678.1446207.12594230734069147905.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106190559.1906130-3-conor@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 6 Nov 2026 19:05:59 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> RISCV_ISA_EXT_BUNDLE actually made sense when it was originally added,
> since it presented a simple interface where users (be that in kernel or
> userspace via things they are presented by the kernel) would check the
> exact extension needed for a feature, rather than muddying the water
> with parent extensions. As a result, the kernel does not track the
> status of the parent extension in the bundle, nor expose it to
> userspace.
>
> [...]
Here is the summary with links:
- [v1] riscv: remove RISCV_ISA_EXT_BUNDLE[_VALIDATE]
https://git.kernel.org/riscv/c/642fb67393c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-11-18 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 19:05 [PATCH v1] riscv: remove RISCV_ISA_EXT_BUNDLE[_VALIDATE] Conor Dooley
2026-11-08 9:50 ` Jisheng Zhang
2026-11-18 3:04 ` Paul Walmsley
2026-11-18 3:40 ` patchwork-bot+linux-riscv [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=179497320678.1446207.12594230734069147905.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@linux.dev \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=guodong.xu@oss.qualcomm.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=thecharlesjenkins@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox