linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	broonie@kernel.org, ard.biesheuvel@linaro.org,
	jonathan.cameron@huawei.com
Subject: Re: [PATCH V2 0/5] Crypto Cleanup
Date: Thu, 17 Jan 2019 18:57:30 -0800	[thread overview]
Message-ID: <20190118025729.GA737@sol.localdomain> (raw)
In-Reply-To: <1547707683-45878-1-git-send-email-wangxiongfeng2@huawei.com>

On Thu, Jan 17, 2019 at 02:47:58PM +0800, Xiongfeng Wang wrote:
> The patchset introduce a helper to (un)register a array of crypto templates.
> The following patches use this helper to simplify the code. This is also
> a preparation for a coming patchset, which will register several crypto
> templates.
> 
> Changelog:
> v1 -> v2: 
> 	rebased to cryptodev, fix some format issue
> 
> Xiongfeng Wang (5):
>   crypto: api - add a helper to (un)register a array of templates
>   crypto: ccm - use template array registering API to simplify the code
>   crypto: gcm - use template array registering API to simplify the code
>   crypto: ctr - use template array registering API to simplify the code
>   crypto: chacha20poly1305 - use template array registering API to
>     simplify the code
> 
>  crypto/algapi.c           | 27 ++++++++++++++++
>  crypto/ccm.c              | 78 ++++++++++++++---------------------------------
>  crypto/chacha20poly1305.c | 37 +++++++++-------------
>  crypto/ctr.c              | 43 +++++++++-----------------
>  crypto/gcm.c              | 73 ++++++++++++++------------------------------
>  include/crypto/algapi.h   |  2 ++
>  6 files changed, 104 insertions(+), 156 deletions(-)
> 
> -- 
> 1.7.12.4
> 

For all 5 patches:

Reviewed-by: Eric Biggers <ebiggers@google.com>

However, you need to fix your email address to be the same in the Author and
Signed-off-by.  Right now it's:

Author: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Signed-off-by: Xiongfeng Wang <xiongfeng.wang@linaro.org>

(checkpatch.pl also warns about this.)

Thanks!

- Eric

      parent reply	other threads:[~2019-01-18  2:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17  6:47 [PATCH V2 0/5] Crypto Cleanup Xiongfeng Wang
2019-01-17  6:47 ` [PATCH V2 1/5] crypto: api - add a helper to (un)register a array of templates Xiongfeng Wang
2019-01-17  6:48 ` [PATCH V2 2/5] crypto: ccm - use template array registering API to simplify the code Xiongfeng Wang
2019-01-17  6:48 ` [PATCH V2 3/5] crypto: gcm " Xiongfeng Wang
2019-01-17  6:48 ` [PATCH V2 4/5] crypto: ctr " Xiongfeng Wang
2019-01-18  2:58   ` Eric Biggers
2019-01-17  6:48 ` [PATCH V2 5/5] crypto: chacha20poly1305 " Xiongfeng Wang
2019-01-18  2:57 ` Eric Biggers [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=20190118025729.GA737@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangxiongfeng2@huawei.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).