From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/3] nvme: support command retry delay for admin command
Date: Sat, 16 Jan 2021 03:40:46 +0900 [thread overview]
Message-ID: <20210115184046.GC2822@localhost.localdomain> (raw)
In-Reply-To: <20210114072254.GA517@lst.de>
On 21-01-14 08:22:54, Christoph Hellwig wrote:
> On Tue, Jan 12, 2021 at 09:06:53AM +0100, Christoph Hellwig wrote:
> > Except for the little wording issue this looks good to me. I'll pick it
> > up for nvme-5.11 and will fix up the commit log.
>
> Given that we never retry admin command right now I've moved this off
> nvme-5.11 into the pending queue.
Thanks for sharing!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-15 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 14:46 [PATCH 0/3] nvme: fixes for command retry Minwoo Im
2021-01-08 14:46 ` [PATCH 1/3] nvme: support command retry delay for admin command Minwoo Im
2021-01-09 20:34 ` Chaitanya Kulkarni
2021-01-10 1:33 ` Minwoo Im
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:47 ` Minwoo Im
2021-01-14 7:22 ` Christoph Hellwig
2021-01-15 18:40 ` Minwoo Im [this message]
2021-01-08 14:46 ` [PATCH 2/3] nvme: check all retry delay times in Identify Controller Minwoo Im
2021-01-12 8:08 ` Christoph Hellwig
2021-01-12 8:40 ` Minwoo Im
2021-01-08 14:46 ` [PATCH 3/3] nvme: add parameter command_retry to enable retry Minwoo Im
2021-01-11 3:47 ` Chao Leng
2021-01-11 12:27 ` Minwoo Im
2021-01-12 9:34 ` Chao Leng
2021-01-12 11:28 ` Minwoo Im
2021-01-12 8:09 ` Christoph Hellwig
2021-01-12 8:44 ` Minwoo Im
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=20210115184046.GC2822@localhost.localdomain \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox