All of lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH V7 0/7] nvme-cli: Introduce nvme-status mapping with errno
Date: Thu, 20 Jun 2019 23:22:18 +0900	[thread overview]
Message-ID: <20190620142218.GC12032@minwooim-desktop> (raw)
In-Reply-To: <20190618131216.3661-1-minwoo.im.dev@gmail.com>

On 19-06-18 22:12:09, Minwoo Im wrote:
> Hi Keith,
> 
> Now it's v7 patchset for the nvme-status mapping with errno.  Chaitanya
> has reviewed for the first five patches, and Sagi has suggested to
> return an error for a case that numrec is different.  The 6th and 7th
> patch will make what Sagi's said.

Hi Keith,

I will put this series to the Github PR for your convenience.

Thanks in advance,
(Also thanks to Sagi and Chaitanya for the reviews :))

      parent reply	other threads:[~2019-06-20 14:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 13:12 [PATCH V7 0/7] nvme-cli: Introduce nvme-status mapping with errno Minwoo Im
2019-06-18 13:12 ` [PATCH V7 1/7] nvme: Do not return in the middle of the subcommand Minwoo Im
2019-06-18 13:12 ` [PATCH V7 2/7] fabrics: " Minwoo Im
2019-06-18 13:12 ` [PATCH V7 3/7] nvme: Return negative error value for internal errors Minwoo Im
2019-06-18 13:12 ` [PATCH V7 4/7] nvme-status: Introduce nvme status module to map errno Minwoo Im
2019-06-18 13:12 ` [PATCH V7 5/7] nvme: Return errno mapped for nvme error status Minwoo Im
2019-06-18 13:12 ` [PATCH V7 6/7] fabrics: return error when discovery retry exhausted Minwoo Im
2019-06-18 13:12 ` [PATCH V7 7/7] fabrics: Return errno mapped for fabrics error status Minwoo Im
2019-06-19 17:01 ` [PATCH V7 0/7] nvme-cli: Introduce nvme-status mapping with errno Sagi Grimberg
2019-06-19 17:05 ` Chaitanya Kulkarni
2019-06-20 14:22 ` Minwoo Im [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=20190620142218.GC12032@minwooim-desktop \
    --to=minwoo.im.dev@gmail.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.