From: Alison Schofield <alison.schofield@intel.com>
To: Raghu H <raghuhack78@gmail.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [STYLE v1 0/3] Fixing check patch styling issues
Date: Thu, 27 Apr 2023 12:46:20 -0700 [thread overview]
Message-ID: <ZErRDPS6f0UKgsyI@aschofie-mobl2> (raw)
In-Reply-To: <20230419111443.231151-1-raghuhack78@gmail.com>
On Wed, Apr 19, 2023 at 11:14:40AM +0000, Raghu H wrote:
Hi Raghu,
Thanks for the cleanup patches.
Sometime maintainers don't want cleanup, but these look good, and
hopefully they can get queued, after you send a v2.
I see Ira already commented to drop the tab reformatting, so drop
that in a v2 of this set.
I notice only 'me' in the 'To;' list here. The cover letter needs
to get the same maintainer list as your patches.
Each patches commit log (now 2 patches) should say 'Issue found with
checkpatch', or something similar. We like to know what tool to credit,
and like that to be in the git history/changelog, not just the cover
letter.
> The following patches are cleanup or fixing the styling issues found
> using checkpatch
>
> In cxl/core/mbox.c, in case of null check failure, returning errno or
> -ENOMEM in this case is good enough, removing the redundant dev_err
> message.
>
> In cxl/core/port.c, there is line of spaces in the definition which
> violates checkpatch coding sytle, restructured the definition to use
> tabs
>
> In cxl/core/region.c, the else is not required after the return
> statement, cleaned it up.
>
> Verified the build and sanity by booting the guest VM using the freshly
> built components.
>
> Raghu H (3):
> cxl/mbox: remove redundant debug msg
> cxl/core/port: Use tabs to fix styling errors
> cxl/core/region:Remove else after return statement
Assumes you are dropping the port changes.
Do this:
$git log --oneline mbox.c
$git log --oneline region.c
Your commit messages 'look' different than the existing message.
Please fix their formatting, in addition to the reword I mention
in patch 1 reply.
Thanks,
Alison
>
> drivers/cxl/core/mbox.c | 4 +---
> drivers/cxl/core/port.c | 18 +++++++++---------
> drivers/cxl/core/region.c | 7 +++----
> 3 files changed, 13 insertions(+), 16 deletions(-)
>
> --
> 2.39.2
>
prev parent reply other threads:[~2023-04-27 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:14 [STYLE v1 0/3] Fixing check patch styling issues Raghu H
2023-04-19 11:14 ` [STYLE v1 1/3] cxl/mbox: remove redundant debug msg Raghu H
2023-04-27 19:05 ` Ira Weiny
2023-04-27 19:32 ` Alison Schofield
2023-04-19 11:14 ` [STYLE v1 2/3] cxl/core/port: Use tabs to fix styling errors Raghu H
2023-04-27 19:06 ` Ira Weiny
2023-04-19 11:14 ` [STYLE v1 3/3] cxl/core/region:Remove else after return statement Raghu H
2023-04-27 19:13 ` Ira Weiny
2023-04-27 19:49 ` Alison Schofield
2023-04-28 0:00 ` RAGHU H
2023-04-27 19:46 ` Alison Schofield [this message]
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=ZErRDPS6f0UKgsyI@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=raghuhack78@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