public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "jaegeuk@google.com" <jaegeuk@google.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries
Date: Wed, 20 Dec 2017 19:20:49 +0000	[thread overview]
Message-ID: <1513797648.2603.33.camel@wdc.com> (raw)
In-Reply-To: <20171220191631.50329-1-jaegeuk@kernel.org>

On Wed, 2017-12-20 at 11:16 -0800, Jaegeuk Kim wrote:
> From: Jaegeuk Kim <jaegeuk@google.com>

Hello Jaegeuk,

For future patch series submissions, please include a cover letter that explains
the purpose of the patch series and please also document the changes between the
different versions of the patch series in the cover letter.

Thanks,

Bart.


  parent reply	other threads:[~2017-12-20 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 19:16 [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries Jaegeuk Kim
2017-12-20 19:16 ` [PATCH 2/2 v3] scsi: ufs: introduce sysfs entries exposing UFS health info Jaegeuk Kim
2017-12-20 22:13   ` [PATCH 2/2 v4] " Jaegeuk Kim
2017-12-21  7:59     ` Greg Kroah-Hartman
2017-12-27  9:00       ` Avri Altman
2017-12-27 13:10         ` Greg Kroah-Hartman
2017-12-28 20:10           ` Jaegeuk Kim
2017-12-20 19:20 ` Bart Van Assche [this message]
2017-12-20 20:16   ` [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries Jaegeuk Kim
2017-12-21  2:37     ` Martin K. Petersen
2017-12-21  7:59       ` gregkh
2017-12-21  7:59 ` 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=1513797648.2603.33.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaegeuk@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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