public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Munsie <imunsie@au1.ibm.com>
To: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
Cc: "Manoj N. Kumar" <manoj@linux.vnet.ibm.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"James.Bottomley" <James.Bottomley@HansenPartnership.com>,
	nab <nab@linux-iscsi.org>, brking <brking@linux.vnet.ibm.com>,
	Daniel Axtens <dja@ozlabs.au.ibm.com>,
	"andrew.donnellan" <andrew.donnellan@au1.ibm.com>,
	mikey <mikey@neuling.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/29] cxlflash: Miscellaneous bug fixes and corrections
Date: Wed, 16 Sep 2015 12:50:22 +1000	[thread overview]
Message-ID: <1442371641-sup-310@delenn.ozlabs.ibm.com> (raw)
In-Reply-To: <8867AAC7-E67D-48B6-93DD-454B96F5979A@linux.vnet.ibm.com>

Hi Matt & Manoj,

Can you also add linuxppc-dev@lists.ozlabs.org to the Cc list for
version 2?

Cheers,
-Ian

Excerpts from Matthew R. Ochs's message of 2015-09-15 06:12:29 +1000:
> > On Sep 13, 2015, at 8:12 PM, Ian Munsie <imunsie@au1.ibm.com> wrote:
> > 
> > Hi Matt & Manoj,
> > 
> > Just a general comment about this series - I'd like to see more detailed
> > commit messages for almost all these patches. Of course James is the
> > scsi maintainer and it's up to him whether to take these as is or not,
> > but generally when you write a commit message for a bug fix you want to
> > explain:
> > 
> > - What problem can occur, possibly including an example
> > - Why it occurs
> > - How this patch addresses it
> > 
> > You don't necessarily need to go overboard because at some point people
> > can just read the code, but some of these patches don't have any detail
> > beyond a single subject line, which is too little.
> > 
> > Speaking of the subject line - if the patch is fixing a bug there should
> > be some indication of that in the subject (it should probably include
> > the word "fix" somewhere). If the subject just states what you are
> > changing then it's not immediately obvious that it is a bug fix.
> 
> This is a reasonable request. Will incorporate your suggestions
> and send out in a v2 series. Thanks for the examples of what you
> would like to see.
> 
> 
> -matt


  reply	other threads:[~2015-09-16  2:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 21:13 [PATCH 00/29] cxlflash: Miscellaneous bug fixes and corrections Matthew R. Ochs
2015-09-14  1:12 ` Ian Munsie
2015-09-14 20:12   ` Matthew R. Ochs
2015-09-16  2:50     ` Ian Munsie [this message]
2015-09-16  3:50       ` Matthew R. Ochs

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=1442371641-sup-310@delenn.ozlabs.ibm.com \
    --to=imunsie@au1.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=dja@ozlabs.au.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=manoj@linux.vnet.ibm.com \
    --cc=mikey@neuling.org \
    --cc=mrochs@linux.vnet.ibm.com \
    --cc=nab@linux-iscsi.org \
    /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