From: Heiko Carstens <hca@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: gor@linux.ibm.com, agordeev@linux.ibm.com,
linux-s390@vger.kernel.org, dengler@linux.ibm.com,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v5 0/2] Rework protected key AES for true asynch support
Date: Wed, 14 May 2025 12:39:49 +0200 [thread overview]
Message-ID: <20250514103949.22307Ac7-hca@linux.ibm.com> (raw)
In-Reply-To: <20250514090955.72370-1-freude@linux.ibm.com>
On Wed, May 14, 2025 at 11:09:53AM +0200, Harald Freudenberger wrote:
> This is a complete rework of the protected key AES (PAES) implementation.
> The goal of this rework is to implement the 4 modes (ecb, cbc, ctr, xts)
> in a real asynchronous fashion:
...
> v5 - Fixed two typos and 1 too long line in the commit message found
> by Holger. Added Acked-by and Reviewed-by.
> Removed patch #3 which updates the crypto engine docu - this
> will go separate. All prepared for picking in the s390 subsystem.
>
> Harald Freudenberger (2):
> s390/cpacf: Rework cpacf_pcc() to return condition code
> s390/crypto: Rework protected key AES for true asynch support
>
> arch/s390/crypto/paes_s390.c | 1812 +++++++++++++++++++++++----------
> arch/s390/include/asm/cpacf.h | 18 +-
> 2 files changed, 1285 insertions(+), 545 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2025-05-14 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 9:09 [PATCH v5 0/2] Rework protected key AES for true asynch support Harald Freudenberger
2025-05-14 9:09 ` [PATCH v5 1/2] s390/cpacf: Rework cpacf_pcc() to return condition code Harald Freudenberger
2025-05-14 9:09 ` [PATCH v5 2/2] s390/crypto: Rework protected key AES for true asynch support Harald Freudenberger
2025-05-26 15:25 ` Thomas Huth
2025-05-27 7:31 ` Harald Freudenberger
2025-05-27 8:21 ` Thomas Huth
2025-05-14 10:39 ` Heiko Carstens [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=20250514103949.22307Ac7-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-s390@vger.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