From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>,
linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-kernel@vger.kernel.org,
Franziska Naepelt <franziska.naepelt@gmail.com>,
Linux SPDX Licenses <linux-spdx@vger.kernel.org>,
James Morris <jmorris@intercode.com.au>,
Steve French <sfrench@samba.org>
Subject: Re: [PATCH] crypto: md4: Fix checkpatch issues
Date: Tue, 6 Jun 2023 19:14:51 +0700 [thread overview]
Message-ID: <ZH8jO0FO2QJ7eGBV@debian.me> (raw)
In-Reply-To: <20230606112610.98149-1-franziska.naepelt@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
On Tue, Jun 06, 2023 at 01:26:10PM +0200, Franziska Naepelt wrote:
> The following checkpatch issues have been fixed:
> - WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
> - ERROR: space required after that ',' (ctx:VxV)
> - ERROR: space prohibited after that open square bracket '['
> - WARNING: space prohibited between function name and open parenthesis '('
> - ERROR: code indent should use tabs where possible
Again, please split up into one patch per fixes, as a patch series.
>
> not fixed:
> - ERROR: space required after that ',' (ctx:VxV)
> in lines: 64, 65, 66 have not ben fixed due to readability
Can you clearly explain why do you skip #define ROUNDx macros?
> -/*
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> * Cryptographic API.
> *
> * MD4 Message Digest Algorithm (RFC1320).
What about removing the license boilerplate text below (and thus convert
to SPDX)? Personally, I prefer having a SPDX conversion series for crypto/
directory instead.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2023-06-06 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230606112610.98149-1-franziska.naepelt@gmail.com>
2023-06-06 12:14 ` Bagas Sanjaya [this message]
2023-06-06 12:18 ` [PATCH] crypto: md4: Fix checkpatch issues Ard Biesheuvel
2023-06-06 12:22 ` Bagas Sanjaya
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=ZH8jO0FO2QJ7eGBV@debian.me \
--to=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=franziska.naepelt@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@intercode.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=sfrench@samba.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