From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Harald Freudenberger <freude@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-crypto@vger.kernel.org,
davem@davemloft.net, dengler@linux.ibm.com
Subject: Re: [PATCH v10 2/5] s390/crypto: New s390 specific protected key hash phmac
Date: Wed, 12 Feb 2025 03:32:26 +0000 [thread overview]
Message-ID: <20250212033226.GA2010357@google.com> (raw)
In-Reply-To: <Z6wUO-8wPTyzF5SK@gondor.apana.org.au>
On Wed, Feb 12, 2025 at 11:23:39AM +0800, Herbert Xu wrote:
> On Wed, Feb 12, 2025 at 11:19:40AM +0800, Herbert Xu wrote:
> >
> > Don't worry about this. It can easily be reverted once a patch
> > using it is submitted.
>
> I just reverted it in cryptodev.
>
Nacked-by: Eric Biggers <ebiggers@kernel.org>
- Eric
next prev parent reply other threads:[~2025-02-12 3:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 16:22 New s390 specific protected key hmac Harald Freudenberger
2025-01-15 16:22 ` [PATCH v10 1/5] s390/crypto: Add protected key hmac subfunctions for KMAC Harald Freudenberger
2025-01-15 16:22 ` [PATCH v10 2/5] s390/crypto: New s390 specific protected key hash phmac Harald Freudenberger
2025-02-09 8:47 ` Herbert Xu
2025-02-09 16:34 ` Eric Biggers
2025-02-10 7:57 ` Herbert Xu
2025-02-10 16:32 ` Eric Biggers
2025-02-10 23:14 ` Herbert Xu
2025-02-12 11:17 ` Harald Freudenberger
2025-02-12 15:20 ` Eric Biggers
2025-02-13 4:08 ` Herbert Xu
2025-02-11 12:09 ` Harald Freudenberger
2025-02-11 15:31 ` Eric Biggers
2025-02-12 3:19 ` Herbert Xu
2025-02-12 3:23 ` Herbert Xu
2025-02-12 3:32 ` Eric Biggers [this message]
2025-02-22 8:23 ` Herbert Xu
2025-01-15 16:22 ` [PATCH v10 3/5] crypto: api - Add crypto_tfm_alg_get_flags() helper inline function Harald Freudenberger
2025-01-15 16:22 ` [PATCH v10 4/5] s390/crypto: Add selftest support for phmac Harald Freudenberger
2025-01-15 16:22 ` [PATCH v10 5/5] crypto: testmgr - Enable phmac selftest Harald Freudenberger
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=20250212033226.GA2010357@google.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).