Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Aditya Parekh <kerneladi@gmail.com>
To: herbert@gondor.apana.org.au
Cc: davem@davemloft.net, trivial@kernel.org,
	linux-crypto@vger.kernel.org, Aditya Parekh <kerneladi@gmail.com>
Subject: [PATCH] Crypto: fixed a comment coding style issue
Date: Sat, 22 Jun 2019 21:40:00 -0400	[thread overview]
Message-ID: <20190623014000.2935-1-kerneladi@gmail.com> (raw)

Fixed a coding style issue.

Signed-off-by: Aditya Parekh <kerneladi@gmail.com>
---
 crypto/fcrypt.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/crypto/fcrypt.c b/crypto/fcrypt.c
index 4e8704405a3b..3828266af0b8 100644
--- a/crypto/fcrypt.c
+++ b/crypto/fcrypt.c
@@ -306,7 +306,8 @@ static int fcrypt_setkey(struct crypto_tfm *tfm, const u8 *key, unsigned int key
 
 #if BITS_PER_LONG == 64  /* the 64-bit version can also be used for 32-bit
 			  * kernels - it seems to be faster but the code is
-			  * larger */
+			  * larger
+			  */
 
 	u64 k;	/* k holds all 56 non-parity bits */
 
-- 
2.17.1


             reply	other threads:[~2019-06-23  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  1:40 Aditya Parekh [this message]
2019-06-24  4:07 ` [PATCH] Crypto: fixed a comment coding style issue Herbert Xu

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=20190623014000.2935-1-kerneladi@gmail.com \
    --to=kerneladi@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=trivial@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