LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: daniel watson <ozzloy@challenge-bot.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:iio:ade7854 surround complex defines in parentheses
Date: Mon, 16 Aug 2021 21:30:38 -0700 [thread overview]
Message-ID: <20210817043038.GA9492@challenge-bot.com> (raw)
In-Reply-To: <YRizb/FGfYpGbpJy@kroah.com>
If this is a false positive from checkpatch, I can submit it as an
example to the checkpatch maintainers. Do you think I should?
On Sun, Aug 15, 2021 at 08:25:51AM +0200, Greg Kroah-Hartman wrote:
> On Sat, Aug 14, 2021 at 07:31:15PM -0700, daniel watson wrote:
> > Error found by checkpatch.pl
>
> What error?
$ git checkout 36a21d5172 drivers/staging/iio/meter/ade7854.h # before
Updated 1 path from 638ccd1543654
$ ./scripts/checkpatch.pl --terse --types COMPLEX_MACRO \
drivers/staging/iio/meter/ade7854.h
drivers/staging/iio/meter/ade7854.h:142: ERROR: Macros with complex
values should be enclosed in parentheses
drivers/staging/iio/meter/ade7854.h:143: ERROR: Macros with complex
values should be enclosed in parentheses
drivers/staging/iio/meter/ade7854.h:144: ERROR: Macros with complex
values should be enclosed in parentheses
total: 3 errors, 0 warnings, 0 checks, 173 lines checked
$ git checkout 143b51a80978 drivers/staging/iio/meter/ade7854.h # after
Updated 1 path from 21c208a36476a
$ ./scripts/checkpatch.pl --terse --types COMPLEX_MACRO \
drivers/staging/iio/meter/ade7854.h
$
> > Signed-off-by: daniel watson <ozzloy@challenge-bot.com>
>
> Capitalize your name?
I can remake this patch with my name capitalized if the patch is worth
remaking. I'll be sure to capitalize in future sign-off lines for
Linux.
> This is not a real change that is needed, just look at the code to
> verify that.
Agreed, this is not a huge change.
I thought small changes were acceptable, if they get rid of errors from
checkpatch. I got that impression from this video
Write and Submit your first Linux kernel Patch
https://youtu.be/LLBrBBImJt4
At around 15 minutes, you create a patch which removes curly braces
from an if-else. That seemed comparable to the change in this
patch. That video was posted over a decade ago, so I would understand
if things are different now.
>
> thanks,
>
> greg k-h
You're welcome! Thank you too, that was a super fast response! I am
happy to get a direct response from you!
next prev parent reply other threads:[~2021-08-17 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 2:31 daniel watson
2021-08-15 6:25 ` Greg Kroah-Hartman
2021-08-17 4:30 ` daniel watson [this message]
2021-08-17 6:12 ` Greg Kroah-Hartman
2021-08-17 8:50 ` Joe Perches
2021-08-17 8:24 ` Fabio M. De Francesco
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=20210817043038.GA9492@challenge-bot.com \
--to=ozzloy@challenge-bot.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--subject='Re: [PATCH] staging:iio:ade7854 surround complex defines in parentheses' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).