From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
ebiggers@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
cleger@rivosinc.com, andybnac@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Add some validation for vector, vector crypto and fp stuff
Date: Thu, 03 Apr 2025 16:20:33 +0000 [thread overview]
Message-ID: <174369723376.2563936.10648565099662367295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312-abide-pancreas-3576b8c44d2c@spud>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Wed, 12 Mar 2025 13:11:43 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Yo,
>
> This series is partly leveraging Clement's work adding a validate
> callback in the extension detection code so that things like checking
> for whether a vector crypto extension is usable can be done like:
> has_extension(<vector crypto>)
> rather than
> has_vector() && has_extension(<vector crypto>)
> which Eric pointed out was a poor design some months ago.
>
> [...]
Here is the summary with links:
- [v4,1/6] RISC-V: add vector extension validation checks
https://git.kernel.org/riscv/c/9324571e9eea
- [v4,2/6] RISC-V: add vector crypto extension validation checks
https://git.kernel.org/riscv/c/38077ec8fc11
- [v4,3/6] RISC-V: add f & d extension validation checks
https://git.kernel.org/riscv/c/12e7fbb6a84e
- [v4,4/6] dt-bindings: riscv: d requires f
https://git.kernel.org/riscv/c/534d813a0620
- [v4,5/6] dt-bindings: riscv: add vector sub-extension dependencies
https://git.kernel.org/riscv/c/e9f1d61a5e18
- [v4,6/6] dt-bindings: riscv: document vector crypto requirements
https://git.kernel.org/riscv/c/a0d857205756
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
ebiggers@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
cleger@rivosinc.com, andybnac@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Add some validation for vector, vector crypto and fp stuff
Date: Thu, 03 Apr 2025 16:20:33 +0000 [thread overview]
Message-ID: <174369723376.2563936.10648565099662367295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312-abide-pancreas-3576b8c44d2c@spud>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Wed, 12 Mar 2025 13:11:43 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Yo,
>
> This series is partly leveraging Clement's work adding a validate
> callback in the extension detection code so that things like checking
> for whether a vector crypto extension is usable can be done like:
> has_extension(<vector crypto>)
> rather than
> has_vector() && has_extension(<vector crypto>)
> which Eric pointed out was a poor design some months ago.
>
> [...]
Here is the summary with links:
- [v4,1/6] RISC-V: add vector extension validation checks
https://git.kernel.org/riscv/c/9324571e9eea
- [v4,2/6] RISC-V: add vector crypto extension validation checks
https://git.kernel.org/riscv/c/38077ec8fc11
- [v4,3/6] RISC-V: add f & d extension validation checks
https://git.kernel.org/riscv/c/12e7fbb6a84e
- [v4,4/6] dt-bindings: riscv: d requires f
https://git.kernel.org/riscv/c/534d813a0620
- [v4,5/6] dt-bindings: riscv: add vector sub-extension dependencies
https://git.kernel.org/riscv/c/e9f1d61a5e18
- [v4,6/6] dt-bindings: riscv: document vector crypto requirements
https://git.kernel.org/riscv/c/a0d857205756
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-04-03 16:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 13:11 [PATCH v4 0/6] Add some validation for vector, vector crypto and fp stuff Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-12 13:11 ` [PATCH v4 1/6] RISC-V: add vector extension validation checks Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-25 13:16 ` Alexandre Ghiti
2025-03-25 13:16 ` Alexandre Ghiti
2025-03-12 13:11 ` [PATCH v4 2/6] RISC-V: add vector crypto " Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-25 13:44 ` Alexandre Ghiti
2025-03-25 13:44 ` Alexandre Ghiti
2025-03-12 13:11 ` [PATCH v4 3/6] RISC-V: add f & d " Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-25 13:48 ` Alexandre Ghiti
2025-03-25 13:48 ` Alexandre Ghiti
2025-03-12 13:11 ` [PATCH v4 4/6] dt-bindings: riscv: d requires f Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-12 13:11 ` [PATCH v4 5/6] dt-bindings: riscv: add vector sub-extension dependencies Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-12 13:11 ` [PATCH v4 6/6] dt-bindings: riscv: document vector crypto requirements Conor Dooley
2025-03-12 13:11 ` Conor Dooley
2025-03-25 13:51 ` Alexandre Ghiti
2025-03-25 13:51 ` Alexandre Ghiti
2025-04-03 16:20 ` patchwork-bot+linux-riscv [this message]
2025-04-03 16:20 ` [PATCH v4 0/6] Add some validation for vector, vector crypto and fp stuff patchwork-bot+linux-riscv
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=174369723376.2563936.10648565099662367295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andybnac@gmail.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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.