public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 10/11] Fix ERROR: else should follow close brace '}'
Date: Tue, 20 Jun 2017 13:22:55 +0800	[thread overview]
Message-ID: <1497936175-4927-1-git-send-email-fbihjmeric@gmail.com> (raw)
In-Reply-To: <1497935984-4406-1-git-send-email-fbihjmeric@gmail.com>

From: Jhih-Ming Hunag <fbihjmeric@gmail.com>

Fixied "ERROR: else should follow close brace '}'".

Signed-off-by: Jhih-Ming Hunag <fbihjmeric@gmail.com>
---
 drivers/staging/ccree/ssi_aead.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c
index d697244..c148d81 100644
--- a/drivers/staging/ccree/ssi_aead.c
+++ b/drivers/staging/ccree/ssi_aead.c
@@ -1919,8 +1919,7 @@ static int config_gcm_context(struct aead_request *req)
 		memcpy (&req_ctx->gcm_len_block.lenA, &temp64, sizeof(temp64));
 		temp64 = cpu_to_be64(cryptlen * 8);
 		memcpy (&req_ctx->gcm_len_block.lenC, &temp64, 8);
-	}
-	else { //rfc4543=>  all data(AAD,IV,Plain) are considered additional data that is nothing is encrypted.
+	} else { //rfc4543=>  all data(AAD,IV,Plain) are considered additional data that is nothing is encrypted.
 		__be64 temp64;
 		temp64 = cpu_to_be64((req->assoclen+GCM_BLOCK_RFC4_IV_SIZE+cryptlen) * 8);
 		memcpy (&req_ctx->gcm_len_block.lenA, &temp64, sizeof(temp64));
-- 
2.7.4

  parent reply	other threads:[~2017-06-20  5:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  5:19 [PATCH 01/11] Fix coding style of driver/staging/ccree/ssi_aead.c ERROR: space required after that Jhih-Ming Huang
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 ` Jhih-Ming Huang [this message]
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=1497936175-4927-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