From: Randy Dunlap <rdunlap@infradead.org>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>
Cc: davem@davemloft.net, franziska.naepelt@gmail.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, bagasdotme@gmail.com
Subject: Re: [PATCH v2] crypto: fcrypt: Fix block comment
Date: Sun, 11 Jun 2023 07:56:03 -0700 [thread overview]
Message-ID: <1c00f4aa-e696-a071-68a7-cdd62d8ba894@infradead.org> (raw)
In-Reply-To: <20230611105331.16570-1-franziska.naepelt@gmail.com>
Hi--
On 6/11/23 03:53, Franziska Naepelt wrote:
> Fix the following checkpatch issue:
> - WARNING: Block comments use a trailing */ on a separate line
>
> Signed-off-by: Franziska Naepelt <franziska.naepelt@gmail.com>
> ---
> v2:
> - Revert SPDX change to address only one logical change
> ---
> crypto/fcrypt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/crypto/fcrypt.c b/crypto/fcrypt.c
> index 95a16e88899b..e9e119bab784 100644
> --- a/crypto/fcrypt.c
> +++ b/crypto/fcrypt.c
> @@ -303,7 +303,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
> + */
The comment doesn't begin with a /* on a line by itself either.
checkpatch isn't always correct.
Maybe it isn't in this case.
I would either make it a correct multi-line comment or not make a change
at all here.
>
> u64 k; /* k holds all 56 non-parity bits */
>
>
> base-commit: 9561de3a55bed6bdd44a12820ba81ec416e705a7
--
~Randy
next prev parent reply other threads:[~2023-06-11 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 11:10 [PATCH] crypto: frcypt Fix checkpatch warnings Franziska Naepelt
2023-06-06 11:36 ` Bagas Sanjaya
2023-06-11 10:53 ` [PATCH v2] crypto: fcrypt: Fix block comment Franziska Naepelt
2023-06-11 14:56 ` Randy Dunlap [this message]
2023-06-12 17:23 ` Franziska Näpelt
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=1c00f4aa-e696-a071-68a7-cdd62d8ba894@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=franziska.naepelt@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=herbert@gondor.apana.org.au \
--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
all inboxes | Powered by JetHome®