From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Keith Busch <kbusch@kernel.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCHv3 1/4] block: add zone specific block statuses
Date: Mon, 21 Sep 2020 06:54:10 +0000 [thread overview]
Message-ID: <SN4PR0401MB35987C8C8D294A37CD12A36E9B3A0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200918194056.GB4030837@dhcp-10-100-145-180.wdl.wdc.com
On 18/09/2020 21:41, Keith Busch wrote:
[...]
>
> Yes, good point. Those updates need to come from this repo
>
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
>
> right? If so, I can send updates there once it looks like this is the
> form that will be committed.
>
I think so yes. Should we also Cc linux-api on this matter?
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
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-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCHv3 1/4] block: add zone specific block statuses
Date: Mon, 21 Sep 2020 06:54:10 +0000 [thread overview]
Message-ID: <SN4PR0401MB35987C8C8D294A37CD12A36E9B3A0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200918194056.GB4030837@dhcp-10-100-145-180.wdl.wdc.com
On 18/09/2020 21:41, Keith Busch wrote:
[...]
>
> Yes, good point. Those updates need to come from this repo
>
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
>
> right? If so, I can send updates there once it looks like this is the
> form that will be committed.
>
I think so yes. Should we also Cc linux-api on this matter?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-09-21 7:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 23:18 [PATCHv3 0/4] zoned block device specific errors Keith Busch
2020-09-17 23:18 ` Keith Busch
2020-09-17 23:18 ` [PATCHv3 1/4] block: add zone specific block statuses Keith Busch
2020-09-17 23:18 ` Keith Busch
2020-09-18 0:29 ` Damien Le Moal
2020-09-18 0:29 ` Damien Le Moal
2020-09-18 13:31 ` Johannes Thumshirn
2020-09-18 13:31 ` Johannes Thumshirn
2020-09-18 19:40 ` Keith Busch
2020-09-18 19:40 ` Keith Busch
2020-09-21 6:54 ` Johannes Thumshirn [this message]
2020-09-21 6:54 ` Johannes Thumshirn
2020-09-17 23:18 ` [PATCHv3 2/4] nvme: translate zone resource errors Keith Busch
2020-09-17 23:18 ` Keith Busch
2020-09-18 0:30 ` Damien Le Moal
2020-09-18 0:30 ` Damien Le Moal
2020-09-18 13:29 ` Johannes Thumshirn
2020-09-18 13:29 ` Johannes Thumshirn
2020-09-17 23:18 ` [PATCHv3 3/4] scsi: update additional sense codes list Keith Busch
2020-09-17 23:18 ` Keith Busch
2020-09-18 0:36 ` Damien Le Moal
2020-09-18 0:36 ` Damien Le Moal
2020-09-17 23:18 ` [PATCHv3 4/4] scsi: handle zone resources errors Keith Busch
2020-09-17 23:18 ` Keith Busch
2020-09-18 0:37 ` Damien Le Moal
2020-09-18 0:37 ` Damien Le Moal
2020-09-22 21:45 ` Martin K. Petersen
2020-09-22 21:45 ` Martin K. Petersen
2020-09-18 0:49 ` [PATCHv3 0/4] zoned block device specific errors Damien Le Moal
2020-09-18 0:49 ` Damien Le Moal
2020-09-22 13:10 ` Christoph Hellwig
2020-09-22 13:10 ` Christoph Hellwig
2020-09-22 21:48 ` Martin K. Petersen
2020-09-22 21:48 ` Martin K. Petersen
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=SN4PR0401MB35987C8C8D294A37CD12A36E9B3A0@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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.