From: Jhih-Ming Huang <fbihjmeric@gmail.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Jhih-Ming Hunag <fbihjmeric@gmail.com>
Subject: [PATCH 01/11] Fix coding style of driver/staging/ccree/ssi_aead.c ERROR: space required after that
Date: Tue, 20 Jun 2017 13:19:44 +0800 [thread overview]
Message-ID: <1497935984-4406-1-git-send-email-fbihjmeric@gmail.com> (raw)
From: Jhih-Ming Hunag <fbihjmeric@gmail.com>
In this series patches, I fix all of the coding style error in
driver/staging/ccree/ssi_aead.c from 54 errors to 0 error.
The first patch fixed 'ERROR: space required after that'.
Signed-off-by: Jhih-Ming Hunag <fbihjmeric@gmail.com>
---
drivers/staging/ccree/ssi_aead.c | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c
index e8936a3..5bc3a53 100644
--- a/drivers/staging/ccree/ssi_aead.c
+++ b/drivers/staging/ccree/ssi_aead.c
@@ -155,7 +155,7 @@ static int ssi_aead_init(struct crypto_aead *tfm)
ctx->auth_mode = ssi_alg->auth_mode;
ctx->drvdata = ssi_alg->drvdata;
dev = &ctx->drvdata->plat_dev->dev;
- crypto_aead_set_reqsize(tfm,sizeof(struct aead_req_ctx));
+ crypto_aead_set_reqsize(tfm, sizeof(struct aead_req_ctx));
/* Allocate key buffer, cache line aligned */
ctx->enckey = dma_alloc_coherent(dev, AES_MAX_KEY_SIZE,
@@ -1566,7 +1566,7 @@ static int config_ccm_adata(struct aead_request *req) {
/* taken from crypto/ccm.c */
/* 2 <= L <= 8, so 1 <= L' <= 7. */
if (2 > l || l > 8) {
- SSI_LOG_ERR("illegal iv value %X\n",req->iv[0]);
+ SSI_LOG_ERR("illegal iv value %X\n", req->iv[0]);
return -EINVAL;
}
memcpy(b0, req->iv, AES_BLOCK_SIZE);
@@ -1862,27 +1862,27 @@ static inline void ssi_aead_dump_gcm(
ctx->cipher_mode, ctx->authsize, ctx->enc_keylen, req->assoclen, req_ctx->cryptlen );
if ( ctx->enckey != NULL ) {
- dump_byte_array("mac key",ctx->enckey, 16);
+ dump_byte_array("mac key", ctx->enckey, 16);
}
- dump_byte_array("req->iv",req->iv, AES_BLOCK_SIZE);
+ dump_byte_array("req->iv", req->iv, AES_BLOCK_SIZE);
- dump_byte_array("gcm_iv_inc1",req_ctx->gcm_iv_inc1, AES_BLOCK_SIZE);
+ dump_byte_array("gcm_iv_inc1", req_ctx->gcm_iv_inc1, AES_BLOCK_SIZE);
- dump_byte_array("gcm_iv_inc2",req_ctx->gcm_iv_inc2, AES_BLOCK_SIZE);
+ dump_byte_array("gcm_iv_inc2", req_ctx->gcm_iv_inc2, AES_BLOCK_SIZE);
- dump_byte_array("hkey",req_ctx->hkey, AES_BLOCK_SIZE);
+ dump_byte_array("hkey", req_ctx->hkey, AES_BLOCK_SIZE);
- dump_byte_array("mac_buf",req_ctx->mac_buf, AES_BLOCK_SIZE);
+ dump_byte_array("mac_buf", req_ctx->mac_buf, AES_BLOCK_SIZE);
- dump_byte_array("gcm_len_block",req_ctx->gcm_len_block.lenA, AES_BLOCK_SIZE);
+ dump_byte_array("gcm_len_block", req_ctx->gcm_len_block.lenA, AES_BLOCK_SIZE);
if (req->src!=NULL && req->cryptlen) {
- dump_byte_array("req->src",sg_virt(req->src), req->cryptlen+req->assoclen);
+ dump_byte_array("req->src", sg_virt(req->src), req->cryptlen+req->assoclen);
}
if (req->dst!=NULL) {
- dump_byte_array("req->dst",sg_virt(req->dst), req->cryptlen+ctx->authsize+req->assoclen);
+ dump_byte_array("req->dst", sg_virt(req->dst), req->cryptlen+ctx->authsize+req->assoclen);
}
}
#endif
--
2.7.4
next reply other threads:[~2017-06-20 5:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 5:19 Jhih-Ming Huang [this message]
2017-06-20 5:20 ` [PATCH 02/11] Fix ERROR: spaces required around that Jhih-Ming Huang
2017-06-20 8:24 ` Dan Carpenter
2017-06-20 5:21 ` [PATCH 03/11] Fix ERROR: space required before the open brace Jhih-Ming Huang
2017-06-20 5:21 ` [PATCH 04/11] Fix ERROR: that open brace { should be on the previous line Jhih-Ming Huang
2017-06-20 5:21 ` [PATCH 05/11] Fix ERROR: space prohibited after that open parenthesis '(' Jhih-Ming Huang
2017-06-20 8:27 ` Dan Carpenter
2017-06-20 5:21 ` [PATCH 06/11] Fix ERROR: space prohibited before that close parenthesis ')' Jhih-Ming Huang
2017-06-20 5:22 ` [PATCH 07/11] Fix ERROR: open brace '{' following function declarations go on the next line Jhih-Ming Huang
2017-06-20 5:22 ` [PATCH 08/11] Fix ERROR: space prohibited before open square bracket '[' Jhih-Ming Huang
2017-06-20 5:22 ` [PATCH 09/11] Fix ERROR: space prohibited before that ',' Jhih-Ming Huang
2017-06-20 5:22 ` [PATCH 10/11] Fix ERROR: else should follow close brace '}' Jhih-Ming Huang
2017-06-20 5:23 ` [PATCH 11/11] Fix ERROR: "foo* bar" should be "foo *bar" Jhih-Ming Huang
2017-06-20 8:20 ` [PATCH 01/11] Fix coding style of driver/staging/ccree/ssi_aead.c ERROR: space required after that Dan Carpenter
2017-06-20 12:27 ` Joe Perches
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=1497935984-4406-1-git-send-email-fbihjmeric@gmail.com \
--to=fbihjmeric@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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