From: Herbert Xu <herbert@gondor.apana.org.au>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, horia.geanta@nxp.com,
dan.douglass@nxp.com, thomas.lendacky@amd.com, gary.hook@amd.com,
harsh@chelsio.com, matthias.bgg@gmail.com,
leosilva@linux.vnet.ibm.com, pfsmorigo@linux.vnet.ibm.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/11] crypto: gcm - add GCM IV size constant
Date: Fri, 22 Sep 2017 18:14:05 +0800 [thread overview]
Message-ID: <20170922101405.GI16270@gondor.apana.org.au> (raw)
In-Reply-To: <20170822080818.12486-1-clabbe.montjoie@gmail.com>
On Tue, Aug 22, 2017 at 10:08:07AM +0200, Corentin Labbe wrote:
> Many GCM users use directly GCM IV size instead of using some constant.
>
> This patch add all IV size constant used by GCM and convert drivers for using them..
>
> Corentin Labbe (11):
> crypto: gcm - add GCM iv size constant
> crypto: caam - Use GCM IV size constant
> crypto: ccp - Use GCM IV size constant
> crypto: nx - Use GCM IV size constant
> crypto: atmel - Use GCM IV size constant
> crypto: bcm - Use GCM IV size constant
> crypto: mediatek - Use GCM IV size constant
> crypto: chelsio - Use GCM IV size constant
> crypto: omap - Use GCM IV size constant
> crypto: gcm - Use GCM IV size constant
> crypto: aesni - Use GCM IV size constant
All applied. Thanks.
--
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:[~2017-09-22 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 8:08 [PATCH 00/11] crypto: gcm - add GCM IV size constant Corentin Labbe
2017-08-22 8:08 ` [PATCH 01/11] " Corentin Labbe
2017-08-22 8:08 ` [PATCH 02/11] crypto: caam - Use " Corentin Labbe
2017-08-22 8:08 ` [PATCH 03/11] crypto: ccp " Corentin Labbe
2017-08-22 8:08 ` [PATCH 04/11] crypto: nx " Corentin Labbe
2017-08-22 8:08 ` [PATCH 05/11] crypto: atmel " Corentin Labbe
2017-08-22 8:08 ` [PATCH 06/11] crypto: bcm " Corentin Labbe
2017-08-22 8:08 ` [PATCH 07/11] crypto: mediatek " Corentin Labbe
2017-08-22 8:08 ` [PATCH 08/11] crypto: chelsio " Corentin Labbe
2017-08-22 8:08 ` [PATCH 09/11] crypto: omap " Corentin Labbe
2017-08-22 8:08 ` [PATCH 10/11] crypto: gcm " Corentin Labbe
2017-08-22 8:08 ` [PATCH 11/11] crypto: aesni " Corentin Labbe
2017-09-22 10:14 ` 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=20170922101405.GI16270@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=benh@kernel.crashing.org \
--cc=clabbe.montjoie@gmail.com \
--cc=dan.douglass@nxp.com \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=harsh@chelsio.com \
--cc=horia.geanta@nxp.com \
--cc=hpa@zytor.com \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthias.bgg@gmail.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pfsmorigo@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@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).