From: Omar Sandoval <osandov@osandov.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH V2 0/8] nvme: misc cleanups
Date: Mon, 4 Mar 2019 11:10:09 -0800 [thread overview]
Message-ID: <20190304191009.GA5450@vader> (raw)
In-Reply-To: <80D74B0F-BB8E-4E83-ACE2-990E3B9389A8@wdc.com>
On Fri, Mar 01, 2019 at 03:59:53PM +0000, Chaitanya Kulkarni wrote:
> Hi Omar,
>
> Everything looks good.
>
> On 2/27/19, 1:50 PM, "Omar Sandoval" <osandov@osandov.com> wrote:
>
> On Wed, Feb 20, 2019 at 08:42:40PM -0800, Chaitanya Kulkarni wrote:
> > Hi Omar,
> > This is a small patch series which follows the blktests coding
> > style format as pointed out by Bart. Also minimizes the overall
> > code for the review.
> >
> > -Regards,
> > Chaitanya
> >
> > Changes since V1:-
> > 1. Add testcase specific error message on failure.
>
> I also made these redirect to $FULL instead of /dev/null. The result is
> pushed to https://github.com/osandov/blktests/commits/nvme-cleanups,
> could you take a quick look?
>
> Also, I assume I can add your signed-off-by to all of these commits?
> Yes, feel free to add that.
Thanks, merged.
prev parent reply other threads:[~2019-03-04 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 4:42 [PATCH V2 0/8] nvme: misc cleanups Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 1/8] nvme/021: use consistent coding style Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 2/8] nvme/022: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 3/8] nvme/023: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 4/8] nvme/024: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 5/8] nvme/025: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 6/8] nvme/026: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 7/8] nvme/027: " Chaitanya Kulkarni
2019-02-21 4:42 ` [PATCH V2 8/8] nvme/028: " Chaitanya Kulkarni
2019-02-27 18:50 ` [PATCH V2 0/8] nvme: misc cleanups Omar Sandoval
2019-03-01 15:59 ` Chaitanya Kulkarni
2019-03-04 19:10 ` Omar Sandoval [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=20190304191009.GA5450@vader \
--to=osandov@osandov.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=linux-block@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