From: patchwork-bot+linux-riscv@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
linux-crypto@vger.kernel.org, jerry.shih@sifive.com,
christoph.muellner@vrull.eu, heiko@sntech.de,
phoebe.chen@sifive.com, andy.chiu@sifive.com, ardb@kernel.org
Subject: Re: [PATCH riscv/for-next] crypto: riscv - add vector crypto accelerated AES-CBC-CTS
Date: Wed, 20 Mar 2024 20:50:39 +0000 [thread overview]
Message-ID: <171096783926.6804.7089388626356276369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213055442.35954-1-ebiggers@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 12 Feb 2024 21:54:42 -0800 you wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Add an implementation of cts(cbc(aes)) accelerated using the Zvkned
> RISC-V vector crypto extension. This is mainly useful for fscrypt,
> where cts(cbc(aes)) is the "default" filenames encryption algorithm. In
> that use case, typically most messages are short and are block-aligned.
> The CBC-CTS variant implemented is CS3; this is the variant Linux uses.
>
> [...]
Here is the summary with links:
- [riscv/for-next] crypto: riscv - add vector crypto accelerated AES-CBC-CTS
https://git.kernel.org/riscv/c/c70dfa4a2723
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-20 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 5:54 [PATCH riscv/for-next] crypto: riscv - add vector crypto accelerated AES-CBC-CTS Eric Biggers
2024-02-14 16:34 ` Ard Biesheuvel
2024-02-14 22:42 ` Eric Biggers
2024-03-20 20:50 ` 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=171096783926.6804.7089388626356276369.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=ardb@kernel.org \
--cc=christoph.muellner@vrull.eu \
--cc=ebiggers@kernel.org \
--cc=heiko@sntech.de \
--cc=jerry.shih@sifive.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=phoebe.chen@sifive.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