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 4/5] crypto: ctr - use template array registering API to simplify the code
Date: Thu, 17 Jan 2019 18:58:01 -0800 [thread overview]
Message-ID: <20190118025800.GB737@sol.localdomain> (raw)
In-Reply-To: <1547707683-45878-5-git-send-email-wangxiongfeng2@huawei.com>
On Thu, Jan 17, 2019 at 02:48:02PM +0800, Xiongfeng Wang wrote:
> Use crypto template array registering API to simplify the code.
>
> Signed-off-by: Xiongfeng Wang <xiongfeng.wang@linaro.org>
> ---
> crypto/ctr.c | 43 +++++++++++++++----------------------------
> 1 file changed, 15 insertions(+), 28 deletions(-)
>
> diff --git a/crypto/ctr.c b/crypto/ctr.c
> index 4c743a9..d9f9d65 100644
> --- a/crypto/ctr.c
> +++ b/crypto/ctr.c
> @@ -171,12 +171,6 @@ static int crypto_ctr_create(struct crypto_template *tmpl, struct rtattr **tb)
> return err;
> }
>
> -static struct crypto_template crypto_ctr_tmpl = {
> - .name = "ctr",
> - .create = crypto_ctr_create,
> - .module = THIS_MODULE,
> -};
> -
> static int crypto_rfc3686_setkey(struct crypto_skcipher *parent,
> const u8 *key, unsigned int keylen)
> {
> @@ -366,36 +360,29 @@ static int crypto_rfc3686_create(struct crypto_template *tmpl,
> goto out;
> }
>
> -static struct crypto_template crypto_rfc3686_tmpl = {
> - .name = "rfc3686",
> - .create = crypto_rfc3686_create,
> - .module = THIS_MODULE,
> +static struct crypto_template crypto_ctr_tmpls[] = {
> + {
> + .name = "ctr",
> + .create = crypto_ctr_create,
> + .module = THIS_MODULE,
> + }, {
> + .name = "rfc3686",
> + .create = crypto_rfc3686_create,
> + .module = THIS_MODULE,
> + },
> };
>
> +
If you resend please also remove the extra blank line here.
- Eric
next prev parent reply other threads:[~2019-01-18 2:58 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 [this message]
2019-01-17 6:48 ` [PATCH V2 5/5] crypto: chacha20poly1305 " Xiongfeng Wang
2019-01-18 2:57 ` [PATCH V2 0/5] Crypto Cleanup Eric Biggers
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=20190118025800.GB737@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