From: Sagi Grimberg <sagi@grimberg.me>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2 v2] nvme-rdma: fix controller reset hang during traffic
Date: Tue, 28 Jul 2020 00:10:26 -0700 [thread overview]
Message-ID: <e6bb2cfc-e253-04ef-e51e-5971565bd82b@grimberg.me> (raw)
In-Reply-To: <20200728065511.GA21572@lst.de>
> Why is this a 2/2 v2, where is the 1/2?
Sent on 7/24/20, 3:10 PM (PST)
Along with:
[PATCH 1/2] nvme-tcp: fix controller reset hang during traffic
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-07-28 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 0:32 [PATCH 2/2 v2] nvme-rdma: fix controller reset hang during traffic Sagi Grimberg
2020-07-28 6:55 ` Christoph Hellwig
2020-07-28 7:10 ` Sagi Grimberg [this message]
2020-07-28 10:50 ` Christoph Hellwig
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=e6bb2cfc-e253-04ef-e51e-5971565bd82b@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).