From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [RFT PATCH 0/3] crypto: sparc - convert to skcipher API
Date: Tue, 15 Oct 2019 01:11:38 -0700 [thread overview]
Message-ID: <20191015081138.GA23837@infradead.org> (raw)
In-Reply-To: <20191012043850.340957-1-ebiggers@kernel.org>
On Fri, Oct 11, 2019 at 09:38:47PM -0700, Eric Biggers wrote:
> This series converts the glue code for the SPARC64 crypto opcodes
> implementations of AES, Camellia, DES, and 3DES modes from the
> deprecated "blkcipher" API to the "skcipher" API. This is needed in
> order for the blkcipher API to be removed.
Not knowing much about the API: do you have an explanation of what the
difference is and why it matters?
> arch/sparc/crypto/aes_glue.c | 310 +++++++++----------
> arch/sparc/crypto/camellia_glue.c | 217 ++++++-------
> arch/sparc/crypto/des_glue.c | 499 ++++++++++++++----------------
> crypto/Kconfig | 5 +-
> 4 files changed, 468 insertions(+), 563 deletions(-)
At least it removes more code than it adds, which always is a good
thing.
next prev parent reply other threads:[~2019-10-15 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 4:38 [RFT PATCH 0/3] crypto: sparc - convert to skcipher API Eric Biggers
2019-10-12 4:38 ` [RFT PATCH 1/3] crypto: sparc/aes " Eric Biggers
2019-10-12 4:38 ` [RFT PATCH 2/3] crypto: sparc/camellia " Eric Biggers
2019-10-12 4:38 ` [RFT PATCH 3/3] crypto: sparc/des " Eric Biggers
2019-10-12 5:12 ` [RFT PATCH 0/3] crypto: sparc " David Miller
[not found] ` <CADxRZqw5PkW0_9s822UeaDO7UEG_rOQ=-c0bnhDOuuYLmLD_+w@mail.gmail.com>
2019-10-12 5:25 ` Eric Biggers
2019-10-15 8:11 ` Christoph Hellwig [this message]
2019-10-15 16:25 ` Eric Biggers
2019-10-18 7:17 ` Anatoly Pugachev
2019-10-18 8:05 ` Herbert Xu
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=20191015081138.GA23837@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=sparclinux@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).