From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Teddy Engel <engel.teddy@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6656: Fix checkpatch unnecessary parentheses
Date: Wed, 12 Jun 2024 07:41:06 +0200 [thread overview]
Message-ID: <fcf77c98-0ee5-45ce-a17f-d68dfba9f7ee@gmail.com> (raw)
Remove unnecessary parentheses - according to checkpatch.pl strict
Signed-off-by: Teddy Engel <engel.teddy@gmail.com>
Hi Teddy,
your patch creates a checkpatch warning:
WARNING: A patch subject line should describe the change not the tool
that found it
The next thing that worries me is that the fix does not increase the
readability of the code for me. I think overview is better with
brackets.
I also think that you are doing two things at a time. You are changing
the TODO file and the brackets.
I would change only the TODO file.
Thanks for your support.
Bye Philipp
next reply other threads:[~2024-06-12 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 5:41 Philipp Hortmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-11 15:22 [PATCH] staging: vt6656: Fix checkpatch unnecessary parentheses Teddy Engel
2024-06-12 6:57 ` Greg Kroah-Hartman
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=fcf77c98-0ee5-45ce-a17f-d68dfba9f7ee@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=engel.teddy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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