Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH V2 0/4] nvme-cli: Introduce nvme-status mapping with errno
Date: Sat, 18 May 2019 11:11:10 +0900	[thread overview]
Message-ID: <20190518021107.GA31204@minwooim-desktop> (raw)
In-Reply-To: <20190513170342.9497-1-minwoo.im.dev@gmail.com>

On 19-05-14 02:03:38, Minwoo Im wrote:
> Hi,
> 
> This patchset introduces nvme-status module to manage mapping
> relationships between nvme error status and errno.  It cannot be
> directly mapped in 1:1, but we can figure out what kind of errors
> happended by the return value of nvme-cli.
> 
> NVMe status fields are 16bits to indicate, but UNIX return value from
> main() will be parsed in 8bits so that we need to do something about
> return value to indicate nvme error status.
> 
> Please review.
> Thanks,
> 
> Changes to previous C1:
>   - make switch-case inline in nvme-status (Chaitanya)
> 
> Minwoo Im (4):
>   nvme.h: Fix typos in status code values
>   nvme-status: Introduce nvme status module to map errno
>   nvme: Return errno mapped for nvme error status
>   fabrics: Return errno mapped for fabrics error status

Ping :)

      parent reply	other threads:[~2019-05-18  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 17:03 [PATCH V2 0/4] nvme-cli: Introduce nvme-status mapping with errno Minwoo Im
2019-05-13 17:03 ` [PATCH V2 1/4] nvme.h: Fix typos in status code values Minwoo Im
2019-05-19 16:48   ` Chaitanya Kulkarni
2019-05-13 17:03 ` [PATCH V2 2/4] nvme-status: Introduce nvme status module to map errno Minwoo Im
2019-05-19 17:42   ` Chaitanya Kulkarni
2019-05-19 17:56     ` Minwoo Im
2019-05-13 17:03 ` [PATCH V2 3/4] nvme: Return errno mapped for nvme error status Minwoo Im
2019-05-19 17:41   ` Chaitanya Kulkarni
2019-05-19 17:53     ` Minwoo Im
2019-05-19 18:00       ` Chaitanya Kulkarni
2019-05-19 19:03         ` Minwoo Im
2019-05-13 17:03 ` [PATCH V2 4/4] fabrics: Return errno mapped for fabrics " Minwoo Im
2019-05-18  2:11 ` 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=20190518021107.GA31204@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox