From: Alison Schofield <alison.schofield@intel.com>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c
Date: Fri, 28 Oct 2022 11:11:33 -0700 [thread overview]
Message-ID: <Y1wbVeLCLZClEQ6L@aschofie-mobl2> (raw)
In-Reply-To: <cover.1666978292.git.tanjubrunostar0@gmail.com>
We know it's a patchset or series, saying so in subject line is
redundant. Perhaps - 'Checkpatch cleanup in rxtx.c'
On Fri, Oct 28, 2022 at 05:40:52PM +0000, Tanjuate Brunostar wrote:
> The fixes are similar, mostly long lines splitting. I had to make
> serveral patches to ease the work of inspectors
^
Please use a spell checker.
>
> v2: fixed a compilation error found by the kernel test robot and
> recompiled the code
Expected to be in reverse order, with latest changes first.
ie. Here you would start with v8
> v3: tends out the error persisted in the second version. this version is
> a correction of that
?
>
> v4: did some corrections as recommended by Greg KH
State what changed. Do not expect your review to go back
hunting for past review comments.
Same for all below.
>
> v5: shortend changelog comments as recommended by Greg KH
>
> v6: did some corrections as recommended by Greg KH
>
> v7: fixed some errors on my changelog comments
>
> v8: fixed some errors pointed out by Philipp Hortmann
>
> Tanjuate Brunostar (6):
> staging: vt6655: fix lines ending in a '('
Move ( to end of line
> staging: vt6655: fix long lines of code in s_uGetRTSCTSDuration
This doesn't match what was actually done
> staging: vt6655: fix long lines of code in s_uFillDataHead
> staging: vt6655: fix long lines of code in s_vGenerateTxParamete
> staging: vt6655: fix long lines of code in the rest of the file
Each commit msg needs to stand alone. The one above only makes
sense (still it's a poor message) when viewed in this patchset.
Once the patches are applied, it must stand alone.
The commit msg should read like a directive. Fix is too general.
Commit msg states what you did, commit log states why you did it.
I see you took 'refactoring' out of the commit messages, but left it
in the commit logs. It doesn't belong in the logs. As another
reviewer pointed out, this is not a refactor.
Alison
>
> drivers/staging/vt6655/rxtx.c | 542 ++++++++++++++++++++--------------
> 1 file changed, 324 insertions(+), 218 deletions(-)
>
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2022-10-28 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 17:40 Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 2/6] staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 3/6] staging: vt6655: refactor long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 4/6] staging: vt6655: refactor long lines of code in s_vGenerateTxParamete Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 5/6] staging: vt6655: refactor long lines of code in the rest of the file Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 6/6] staging: vt6655: fix lines of code ending in a '(' Tanjuate Brunostar
2022-10-28 18:11 ` Alison Schofield [this message]
2022-10-28 18:17 ` [PATCH v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c Tanju Brunostar
2022-10-29 2:28 ` 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=Y1wbVeLCLZClEQ6L@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@gmail.com \
/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®