All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hch@lst.de" <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCHv2 2/2] nvme: translate zone resource errors
Date: Thu, 17 Sep 2020 07:48:02 +0200	[thread overview]
Message-ID: <20200917054802.GA31594@lst.de> (raw)
In-Reply-To: <20200916210054.GB3676296@dhcp-10-100-145-180.wdl.wdc.com>

On Wed, Sep 16, 2020 at 02:00:54PM -0700, Keith Busch wrote:
> I believe it's safe to use for the completion side since the special
> handling is only for submission errors. But I agree this type of double
> meaning could invite confusion. I'll send a v3 with your suggestion and
> we'll see how that goes.

Two remarks:  Can you include the scsi patch for Damien so that ZNS
and ZBC/ZAC are handled together?  Should we use a separate status
for active vs open zones?

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-09-17  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 18:12 [PATCHv2 1/2] block: map BLK_STS_ZONE_RESOURCE to errno Keith Busch
2020-09-15 18:12 ` [PATCHv2 2/2] nvme: translate zone resource errors Keith Busch
2020-09-15 23:56   ` Damien Le Moal
2020-09-16 21:00     ` Keith Busch
2020-09-17  5:48       ` hch [this message]
2020-09-17  6:14         ` Damien Le Moal
2020-09-15 23:59 ` [PATCHv2 1/2] block: map BLK_STS_ZONE_RESOURCE to errno Damien Le Moal

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=20200917054802.GA31594@lst.de \
    --to=hch@lst.de \
    --cc=Damien.LeMoal@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.