From: Vasily Gorbik <gor@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/3] s390/crypto: Enable CONTEXT_ANALYSIS
Date: Mon, 17 Aug 2026 19:34:11 +0200 [thread overview]
Message-ID: <ttjxcsz@ub.hpns> (raw)
In-Reply-To: <ttjx5j8@ub.hpns>
On Mon, Aug 17, 2026 at 04:57:08PM +0200, Vasily Gorbik wrote:
> On Tue, Aug 04, 2026 at 01:37:33PM +0200, Heiko Carstens wrote:
> > Enable CONTEXT_ANALYSYS for s390's crypto code.
...
> > Heiko Carstens (3):
> > s390/crypto: Rework ctr_aes_crypt() to remove conditional locking
> > s390/crypto: Rework ctr_paes_do_crypt() to remove conditional locking
> > s390/crypto: Enable CONTEXT_ANALYSIS
> >
> > arch/s390/crypto/Makefile | 2 +
> > arch/s390/crypto/aes_s390.c | 54 +++++++++++-------
> > arch/s390/crypto/paes_s390.c | 104 ++++++++++++++++++++---------------
> > 3 files changed, 97 insertions(+), 63 deletions(-)
>
> Applied, thank you!
This series was applied too early. Harald's rework should go in first, so I'm dropping this for now.
prev parent reply other threads:[~2026-08-17 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 11:37 [PATCH 0/3] s390/crypto: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-04 11:37 ` [PATCH 1/3] s390/crypto: Rework ctr_aes_crypt() to remove conditional locking Heiko Carstens
2026-08-04 11:44 ` sashiko-bot
2026-08-04 11:37 ` [PATCH 2/3] s390/crypto: Rework ctr_paes_do_crypt() " Heiko Carstens
2026-08-04 11:47 ` sashiko-bot
2026-08-04 12:47 ` Heiko Carstens
2026-08-05 8:47 ` Harald Freudenberger
2026-08-04 11:37 ` [PATCH 3/3] s390/crypto: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-04 11:45 ` sashiko-bot
2026-08-15 0:59 ` [PATCH 0/3] " Herbert Xu
2026-08-17 7:35 ` Harald Freudenberger
2026-08-17 14:57 ` Vasily Gorbik
2026-08-17 17:34 ` Vasily Gorbik [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=ttjxcsz@ub.hpns \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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.