public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, Raghu H <raghuhack78@gmail.com>
Cc: linux-cxl@vger.kernel.org, ira.weiny@intel.com,
	bwidawsk@kernel.org, dan.j.williams@intel.com,
	vishal.l.verma@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc
Date: Wed, 3 May 2023 19:26:24 -0700	[thread overview]
Message-ID: <ZFMX0K4jeUIBOo7D@aschofie-mobl2> (raw)
In-Reply-To: <dtmb3d2dmcqh2djc4jebd2s7uwhw6l7nyfqgo7o34bhn7gzhzd@jmhb5g7edce4>

On Wed, May 03, 2023 at 03:36:50PM -0700, Davidlohr Bueso wrote:
> On Fri, 28 Apr 2023, Raghu H wrote:
> 
> > Issue found with checkpatch
> 
> fyi for both patches, these are not "issues" - you can remove it, or the line altogether.
> 
> Thanks,
> Davidlohr

Hi Raghu,

Perhaps this patchset got you more attention than you may have expected ;)
So, this is an example of when reviewers disagree. I asked you to note
that checkpatch found these 'issues' and David disagrees.

If David had known I'd asked you to update the commit log to include the
checkpatch credit, he may have ignored it, or maybe not. I don't find
the word 'issue' to be misused. There are many flavors of this phrase used
in kernel commit logs that address checkpatch found issues.

The way the next round of reviewers knows what the first round asked
for is by looking at the changelog. (And, if they need more detail, they
pull up the previous patchset discussion.)

The changelog in the cover letter, or per patch, needs to explicitly
say what has changed.

The v2 says this:

>> v2 changes:
>> Thanks Alison, Ira for your comments, modified the v1 patches as suggested.
>> Dropped the patch containing tab changes in port.c

Next time, be more specific, like this:

v2 changes:
- Update commit logs to credit checkpatch (Alison)
- Update commit msgs to conform to subsystem style (Alison)
- Drop the patch containing tab changes in port.c (Ira)

Thanks,
Alison




  reply	other threads:[~2023-05-04  2:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  1:22 [PATCH v2 0/2] Fixing check patch styling issues Raghu H
2023-04-28  1:22 ` [PATCH v2 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc Raghu H
2023-05-01 14:52   ` Dave Jiang
2023-05-03 17:57   ` Verma, Vishal L
2023-05-03 18:32   ` Fabio M. De Francesco
2023-05-03 22:03     ` Alison Schofield
2023-05-04 10:46       ` Fabio M. De Francesco
2023-05-04 15:23         ` Alison Schofield
2023-05-08  4:12           ` RAGHU H
2023-05-03 22:36   ` Davidlohr Bueso
2023-05-04  2:26     ` Alison Schofield [this message]
2023-04-28  1:22 ` [PATCH v2 2/2] cxl/region: Remove else after return statement Raghu H
2023-05-01 14:53   ` Dave Jiang
2023-05-03 17:58     ` Verma, Vishal L

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=ZFMX0K4jeUIBOo7D@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raghuhack78@gmail.com \
    --cc=vishal.l.verma@intel.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