From: Ming Lei <ming.lei@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: 许春光 <brookxu.cn@gmail.com>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] nvme-tcp: fix hung issues for deleting
Date: Tue, 13 Jun 2023 09:01:31 +0800 [thread overview]
Message-ID: <ZIe/66eA5TMeYZ1U@ovpn-8-16.pek2.redhat.com> (raw)
In-Reply-To: <7a17d0f9-c624-2b30-476e-1a039f978c4e@grimberg.me>
Hi Sagi,
On Mon, Jun 12, 2023 at 09:36:53AM +0300, Sagi Grimberg wrote:
>
...
> >
> > Not yet, will do it.
>
> Would like it to get to the next pull request going out this week...
The two patches have been sent out:
https://lore.kernel.org/linux-nvme/20230613005847.1762378-1-ming.lei@redhat.com/T/#t
thanks,
Ming
next prev parent reply other threads:[~2023-06-13 1:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 10:59 brookxu.cn
2023-05-29 10:59 ` [RFC PATCH 1/4] nvme: unfreeze while exit from recovery or resetting brookxu.cn
2023-05-29 10:59 ` [RFC PATCH 2/4] nvme: donot retry request for NVME_CTRL_DELETING_NOIO brookxu.cn
2023-05-29 10:59 ` [RFC PATCH 3/4] nvme: optimize nvme_check_ready() " brookxu.cn
2023-05-29 10:59 ` [RFC PATCH 4/4] nvme-tcp: remove admin_q quiescing from nvme_tcp_teardown_io_queues brookxu.cn
2023-06-05 23:09 ` [RFC PATCH 0/4] nvme-tcp: fix hung issues for deleting Sagi Grimberg
2023-06-06 14:32 ` 许春光
2023-06-06 14:41 ` 许春光
2023-06-06 15:14 ` Ming Lei
2023-06-07 4:09 ` 许春光
2023-06-08 0:56 ` Ming Lei
2023-06-08 2:48 ` 许春光
2023-06-08 13:51 ` Ming Lei
2023-06-09 3:17 ` 许春光
2023-06-09 3:23 ` 许春光
2023-06-11 8:11 ` Sagi Grimberg
2023-06-12 1:33 ` Ming Lei
2023-06-12 6:36 ` Sagi Grimberg
2023-06-13 1:01 ` Ming Lei [this message]
2023-06-12 8:24 ` 许春光
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=ZIe/66eA5TMeYZ1U@ovpn-8-16.pek2.redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=brookxu.cn@gmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®