linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	thomas.lendacky@amd.com, gary.hook@amd.com, arno@natisbad.org,
	matthias.bgg@gmail.com, giovanni.cabiddu@intel.com,
	salvatore.benedetto@intel.com, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, qat-linux@intel.com
Subject: Re: [PATCH v2 4/9] crypto: marvell - Use IPAD/OPAD constant
Date: Fri, 19 May 2017 11:17:24 +0200	[thread overview]
Message-ID: <20170519111724.3933c91d@bbrezillon> (raw)
In-Reply-To: <20170519065331.27670-5-clabbe.montjoie@gmail.com>

On Fri, 19 May 2017 08:53:26 +0200
Corentin Labbe <clabbe.montjoie@gmail.com> wrote:

> This patch simply replace all occurrence of HMAC IPAD/OPAD value by their
> define.
> 
> Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>

Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>

> ---
>  drivers/crypto/marvell/hash.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/crypto/marvell/hash.c b/drivers/crypto/marvell/hash.c
> index 77c0fb936f47..e61b08566093 100644
> --- a/drivers/crypto/marvell/hash.c
> +++ b/drivers/crypto/marvell/hash.c
> @@ -12,6 +12,7 @@
>   * by the Free Software Foundation.
>   */
>  
> +#include <crypto/hmac.h>
>  #include <crypto/md5.h>
>  #include <crypto/sha.h>
>  
> @@ -1164,8 +1165,8 @@ static int mv_cesa_ahmac_pad_init(struct ahash_request *req,
>  	memcpy(opad, ipad, blocksize);
>  
>  	for (i = 0; i < blocksize; i++) {
> -		ipad[i] ^= 0x36;
> -		opad[i] ^= 0x5c;
> +		ipad[i] ^= HMAC_IPAD_VALUE;
> +		opad[i] ^= HMAC_OPAD_VALUE;
>  	}
>  
>  	return 0;

  reply	other threads:[~2017-05-19  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  6:53 [PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 1/9] crypto: add hmac " Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 2/9] crypto: brcm - Use " Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 3/9] crypto: ixp4xx " Corentin Labbe
     [not found] ` <20170519065331.27670-1-clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-19  6:53   ` [PATCH v2 4/9] crypto: marvell " Corentin Labbe
2017-05-19  9:17     ` Boris Brezillon [this message]
2017-05-19  6:53 ` [PATCH v2 5/9] crypto: mv_cesa " Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 6/9] crypto: omap-sham " Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 7/9] crypto: qat " Corentin Labbe
2017-05-19  6:53 ` [PATCH v2 8/9] crypto: mediatek " Corentin Labbe
2017-05-19  9:11   ` Matthias Brugger
2017-05-19  6:53 ` [PATCH v2 9/9] crypto: ccp " Corentin Labbe
2017-05-19 20:32   ` Gary R Hook
2017-05-23  5:03 ` [PATCH v2 0/9] crypto: add HMAC " Herbert Xu

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=20170519111724.3933c91d@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=arno@natisbad.org \
    --cc=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gary.hook@amd.com \
    --cc=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --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=matthias.bgg@gmail.com \
    --cc=qat-linux@intel.com \
    --cc=salvatore.benedetto@intel.com \
    --cc=thomas.lendacky@amd.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;
as well as URLs for NNTP newsgroup(s).