linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
	"Elliott, Robert" <elliott@hpe.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	Logan Gunthorpe <logang@deltatee.com>,
	Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH blktests v3 0/2] nmve/018 fixes
Date: Mon, 3 Feb 2020 13:40:52 -0800	[thread overview]
Message-ID: <20200203214052.GA1025074@vader> (raw)
In-Reply-To: <20200203164049.140280-1-dwagner@suse.de>

On Mon, Feb 03, 2020 at 05:40:47PM +0100, Daniel Wagner wrote:
> changes from v2:
>   - fixed another typo (argh!)
>   - added reviewed-by tag from Keith
> 
> changes from v1:
>   - added reviewed-by tag from Logan
>   - patch #2 fixed typo in commit message
>   - patch #2 reworded error message as suggested by Robert
> 
> changes from v0:
>   - added "nmve/018: Reword misleading error message"
> 
> Daniel Wagner (2):
>   nvme/018: Ignore message generated by nvme read
>   nvme/018: Reword misleading error message
> 
>  tests/nvme/018 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Thanks, applied and pushed.

      parent reply	other threads:[~2020-02-03 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 16:40 [PATCH blktests v3 0/2] nmve/018 fixes Daniel Wagner
2020-02-03 16:40 ` [PATCH blktests v3 1/2] nvme/018: Ignore message generated by nvme read Daniel Wagner
2020-02-03 21:08   ` Chaitanya Kulkarni
2020-02-03 16:40 ` [PATCH blktests v3 2/2] nvme/018: Reword misleading error message Daniel Wagner
2020-02-03 21:08   ` Chaitanya Kulkarni
2020-02-03 21:40 ` 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=20200203214052.GA1025074@vader \
    --to=osandov@osandov.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=dwagner@suse.de \
    --cc=elliott@hpe.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=osandov@fb.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;
as well as URLs for NNTP newsgroup(s).