From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, Kirill Marinushkin <k.marinushkin@gmail.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
keyrings@vger.kernel.org
Subject: Re: KEYS: Use skcipher for big keys
Date: Wed, 22 Jun 2016 15:23:14 +0100 [thread overview]
Message-ID: <687.1466605394@warthog.procyon.org.uk> (raw)
In-Reply-To: <20160622141353.GA456@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> I'm in the process of removing blkcipher/ablkcipher which have
> been replaced with skcipher. It would be nice if we stop adding
> new users of these two interfaces :)
>
> Anyway, if you guys are OK with this patch I'd like to push it
> through cryptodev so I can carry on with the removal of blkcipher.
As long as it only touches the big_key code inside keyrings, I think that's
fine.
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2016-06-22 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 14:13 KEYS: Use skcipher for big keys Herbert Xu
2016-06-22 14:23 ` David Howells [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=687.1466605394@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=k.marinushkin@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@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