From: Stephan Mueller <smueller@chronox.de>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: dhowells@redhat.com, herbert@gondor.apana.org.au,
linux-api@vger.kernel.org, marcel@holtmann.org,
mathew.j.martineau@linux.intel.com, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
dwmw2@infradead.org, davem@davemloft.net
Subject: Re: [PATCH v8 0/6] crypto: algif - add akcipher
Date: Fri, 24 Jun 2016 08:07:46 +0200 [thread overview]
Message-ID: <9244921.hMLs59jgKA@tauon.atsec.com> (raw)
In-Reply-To: <146672252642.23101.15972023870303797249.stgit@tstruk-mobl1.ra.intel.com>
Am Donnerstag, 23. Juni 2016, 15:55:26 schrieb Tadeusz Struk:
Hi Tadeusz,
> First four patches are a resend algif_akcipher from
> Stephan Mueller, with minor changes after rebase on top of 4.7-rc1.
The first four patches:
Acked-by: Stephan Mueller <smueller@chronox.de>
Ciao
Stephan
prev parent reply other threads:[~2016-06-24 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 22:55 [PATCH v8 0/6] crypto: algif - add akcipher Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 1/6] crypto: AF_ALG -- add sign/verify API Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 2/6] crypto: AF_ALG -- add setpubkey setsockopt call Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 3/6] crypto: AF_ALG -- add asymmetric cipher interface Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 4/6] crypto: algif_akcipher - enable compilation Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 5/6] crypto: algif_akcipher - add ops_nokey Tadeusz Struk
2016-06-23 22:55 ` [PATCH v8 6/6] crypto: AF_ALG - add support for key_id Tadeusz Struk
2016-06-24 1:01 ` kbuild test robot
2016-06-29 18:43 ` Mat Martineau
2016-07-05 20:27 ` Tadeusz Struk
2016-07-06 19:38 ` Mat Martineau
2016-07-08 15:21 ` Tadeusz Struk
2016-07-08 16:38 ` Mat Martineau
2016-07-08 17:26 ` Tadeusz Struk
2016-06-24 6:07 ` Stephan Mueller [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=9244921.hMLs59jgKA@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mathew.j.martineau@linux.intel.com \
--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