Transferring applied X.509 patches from crypto/next to security/next

2016-02-08 Thread David Howells
Herbert Xu wrote: > > Hmmm... That means that the crypto branch and the security branch are going > > to conflict. > > I thought you were OK with it going in now as you said that you'll > fix it up later. Sorry for the misunderstanding. Do you want me to > revert? If you can back them out, I

[PATCH 0/2] crypto: atmel-sha - fix .import()/.export() implementation

2016-02-08 Thread Cyrille Pitchen
This series of patches includes two fixes for the atmel-sha.c driver. The first one fixes the implementation of the import/export hooks, which did not pass the recent updates in testmgr.c (partial update exercise). The new implementation now passes the tcrypt tests: tested with next-20160208

[PATCH 2/2] crypto: atmel-sha - fix race in atmel_sha_final()

2016-02-08 Thread Cyrille Pitchen
When (!ctx->bufcnt && !(ctx->flags & SHA_FLAGS_PAD)), the former source code used to set the SHA_FLAGS_BUSY without checking whether this flag was already set. If so, the hardware is already processing another hash request so the processing of the req argument of atmel_sha_final() should be delayed

[PATCH 1/2] crypto: atmel-sha - fix .import()/.export() implementation

2016-02-08 Thread Cyrille Pitchen
Using only the digest, digcnt[], bufcnt and buffer[] fields of the struct atmel_sha_reqctx was not enough to import/export the request state, so now we use the whole structure. Signed-off-by: Cyrille Pitchen --- drivers/crypto/atmel-sha.c | 44 ++-- 1 file

[PATCH 2/2] crypto: extended acomp api for supporting deflate algorithm parameters

2016-02-08 Thread Giovanni Cabiddu
Signed-off-by: Giovanni Cabiddu --- crypto/acompress.c | 16 + include/crypto/acompress.h | 116 +++ include/crypto/internal/acompress.h | 24 +++ 3 files changed, 156 insertions(+), 0 deletions(-) diff --git a/crypto/acompre

[PATCH 1/2] crypto: add asynchronous compression api

2016-02-08 Thread Giovanni Cabiddu
Signed-off-by: Giovanni Cabiddu --- crypto/Kconfig | 10 ++ crypto/Makefile |2 + crypto/acompress.c | 118 crypto/crypto_user.c| 21 +++ include/crypto/acompress.h | 263

[PATCH 0/2] crypto: asynchronous compression api

2016-02-08 Thread Giovanni Cabiddu
The following patch set introduces acomp, a generic asynchronous (de)compression api. What is proposed is a new crypto type called crypto_acomp_type, plus a new struct acomp_alg and struct crypto_acomp, together with number of helper functions to register acomp type algorithms and allocate tfm ins

[PATCH v2 1/2] dt/bindings: Add bindings for the PIC32 random number generator

2016-02-08 Thread Joshua Henderson
Document the devicetree bindings for the random number generator found on Microchip PIC32 class devices. Signed-off-by: Joshua Henderson Acked-by: Rob Herring --- .../bindings/rng/microchip,pic32-rng.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644 D

[PATCH v2 2/2] rng: pic32-rng: Add PIC32 RNG hardware driver

2016-02-08 Thread Joshua Henderson
Add support for the hardware true random number generator peripheral found on PIC32. Signed-off-by: Joshua Henderson Signed-off-by: Purna Chandra Mandal --- Changes since v1: - Reorder includes to be alphabetic. - Drop use of PRNG and only use TRNG. - Fix dangling clock r

Re: Transferring applied X.509 patches from crypto/next to security/next

2016-02-08 Thread Mimi Zohar
Hi Herbert, On Mon, 2016-02-08 at 13:58 +, David Howells wrote: > Herbert Xu wrote: > > > > Hmmm... That means that the crypto branch and the security branch are > > > going > > > to conflict. > > > > I thought you were OK with it going in now as you said that you'll > > fix it up later.

Re: [PATCH v2 2/2] rng: pic32-rng: Add PIC32 RNG hardware driver

2016-02-08 Thread Daniel Thompson
On Mon, Feb 08, 2016 at 02:17:53PM -0700, Joshua Henderson wrote: > Add support for the hardware true random number generator > peripheral found on PIC32. > > Signed-off-by: Joshua Henderson > Signed-off-by: Purna Chandra Mandal Reviewed-by: Daniel Thompson > --- > Changes since v1: > -

Re: Transferring applied X.509 patches from crypto/next to security/next

2016-02-08 Thread James Morris
On Mon, 8 Feb 2016, David Howells wrote: > Herbert Xu wrote: > > > > Hmmm... That means that the crypto branch and the security branch are > > > going > > > to conflict. > > > > I thought you were OK with it going in now as you said that you'll > > fix it up later. Sorry for the misunderstan