From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>
Subject: [PATCH] crypto: fix semicolon.cocci warnings
Date: Wed, 15 Jun 2016 19:13:25 +0800 [thread overview]
Message-ID: <20160615111325.GA68889@ivytown2> (raw)
In-Reply-To: <201606151923.o07hQ3Ki%fengguang.wu@intel.com>
crypto/drbg.c:1637:39-40: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Stephan Mueller <smueller@chronox.de>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
drbg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/crypto/drbg.c
+++ b/crypto/drbg.c
@@ -1634,7 +1634,7 @@ static int drbg_fini_sym_kernel(struct d
drbg->ctr_handle = NULL;
if (drbg->ctr_req)
- skcipher_request_free(drbg->ctr_req);;
+ skcipher_request_free(drbg->ctr_req);
drbg->ctr_req = NULL;
kfree(drbg->ctr_null_value_buf);
next prev parent reply other threads:[~2016-06-15 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 11:13 [cryptodev:master 47/51] crypto/drbg.c:1637:39-40: Unneeded semicolon kbuild test robot
2016-06-15 11:13 ` kbuild test robot [this message]
2016-06-15 11:40 ` [PATCH] crypto: fix semicolon.cocci warnings Stephan Mueller
2016-06-20 11:33 ` Herbert Xu
2019-11-01 8:24 [cryptodev:master 150/163] drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:558:52-53: Unneeded semicolon kbuild test robot
2019-11-01 8:24 ` [PATCH] crypto: fix semicolon.cocci warnings kbuild test robot
2019-11-01 8:52 Julia Lawall
2019-11-01 12:50 ` Corentin Labbe
2019-11-08 15:20 ` Herbert Xu
2021-12-18 13:25 kernel test robot
2021-12-24 3:28 ` Herbert Xu
2022-01-04 21:14 ` Peter Gonda
2022-01-05 0:29 ` Herbert Xu
2022-01-05 15:20 ` Peter Gonda
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=20160615111325.GA68889@ivytown2 \
--to=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
/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).