Re: [PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant

2017-05-22 Thread Herbert Xu
On Fri, May 19, 2017 at 08:53:22AM +0200, Corentin Labbe wrote: > Hello > > Many HMAC users directly use directly 0x36/0x5c values. > It's better with crypto to use a name instead of directly some crypto > constant. > > Changes since v1: > - Moved constant to include/crypto/hmac.h > - Added to

Re: [PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant

2017-05-22 Thread Herbert Xu
On Fri, May 19, 2017 at 08:53:22AM +0200, Corentin Labbe wrote: > Hello > > Many HMAC users directly use directly 0x36/0x5c values. > It's better with crypto to use a name instead of directly some crypto > constant. > > Changes since v1: > - Moved constant to include/crypto/hmac.h > - Added to

[PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant

2017-05-19 Thread Corentin Labbe
Hello Many HMAC users directly use directly 0x36/0x5c values. It's better with crypto to use a name instead of directly some crypto constant. Changes since v1: - Moved constant to include/crypto/hmac.h - Added to includes Corentin Labbe (9): crypto: add hmac IPAD/OPAD constant crypto: brcm

[PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant

2017-05-19 Thread Corentin Labbe
Hello Many HMAC users directly use directly 0x36/0x5c values. It's better with crypto to use a name instead of directly some crypto constant. Changes since v1: - Moved constant to include/crypto/hmac.h - Added to includes Corentin Labbe (9): crypto: add hmac IPAD/OPAD constant crypto: brcm