From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"jaegeuk@google.com" <jaegeuk@google.com>
Subject: Re: [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries
Date: Thu, 21 Dec 2017 08:59:25 +0100 [thread overview]
Message-ID: <20171221075925.GA9645@kroah.com> (raw)
In-Reply-To: <yq14lokhklo.fsf@oracle.com>
On Wed, Dec 20, 2017 at 09:37:39PM -0500, Martin K. Petersen wrote:
>
> >> 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.
> >
> > Yup, I'll be aware of it. Thank you for the advice.
>
> These look good to me.
>
> Greg: Jaegeuk didn't carry over your review tags (despite the pretty
> modest tweaks). Can I add your Reviewed-by: to these two when I queue
> them up?
Yes, please do, they look fine to me.
greg k-h
next prev parent reply other threads:[~2017-12-21 7:59 UTC|newest]
Thread overview: 13+ 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 ` [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries Bart Van Assche
2017-12-20 20:16 ` Jaegeuk Kim
2017-12-21 2:37 ` Martin K. Petersen
2017-12-21 2:37 ` Martin K. Petersen
2017-12-21 7:59 ` gregkh [this message]
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=20171221075925.GA9645@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Bart.VanAssche@wdc.com \
--cc=jaegeuk@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.