From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: tadeusz.struk@intel.com, marcel@holtmann.org,
dwmw2@infradead.org, linux-api@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] crypto: add algif_akcipher user space API
Date: Tue, 26 Jan 2016 19:12:09 +0800 [thread overview]
Message-ID: <20160126111209.GA21069@gondor.apana.org.au> (raw)
In-Reply-To: <63219617.tVA5DWIBaO@positron.chronox.de>
On Mon, Jan 25, 2016 at 10:34:53PM +0100, Stephan Mueller wrote:
> Am Freitag, 18. Dezember 2015, 00:49:57 schrieb Stephan Mueller:
>
> Hi Herbert,
>
> [...]
>
> > Changes v3:
> > * fix hack in alg_setkey and alg_setsockopt by avoding branches for
> > setkey and setpubkey as pointed out by Marcel Holtmann
> > * removal of patch for fixing SGL handling as this is already included
>
> I have ported the code to 4.5. Shall I wait for comments from you for the
> current code or shall I post v4 for the current cryptodev tree?
Until the objections in
http://www.gossamer-threads.com/lists/linux/kernel/2333253
are resolved I'm not taking any patches that export akcipher
via algif.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2016-01-26 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 23:49 Stephan Mueller
2015-12-17 23:50 ` [PATCH v3 1/4] crypto: AF_ALG -- add sign/verify API Stephan Mueller
2015-12-17 23:50 ` [PATCH v3 2/4] crypto: AF_ALG -- add setpubkey setsockopt call Stephan Mueller
2015-12-17 23:51 ` [PATCH v3 3/4] crypto: AF_ALG -- add asymmetric cipher interface Stephan Mueller
2015-12-17 23:51 ` [PATCH v3 4/4] crypto: algif_akcipher - enable compilation Stephan Mueller
2016-01-25 21:34 ` [PATCH v3 0/4] crypto: add algif_akcipher user space API Stephan Mueller
2016-01-26 11:12 ` Herbert Xu [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=20160126111209.GA21069@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dwmw2@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®