From: Christoph Hellwig <hch@infradead.org>
To: Chris Leech <cleech@redhat.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org,
John Meneghini <jmeneghi@redhat.com>
Subject: Re: [PATCH v2 1/1] nvme-tcp: fence TCP socket on receive error
Date: Wed, 5 Apr 2023 08:21:39 -0700 [thread overview]
Message-ID: <ZC2SAy1YtT63JK8T@infradead.org> (raw)
In-Reply-To: <20230321163025.9437-1-cleech@redhat.com>
Thanks,
applied to nvme-6.4.
Let me know if you really need this in 6.3, but it seems like we're
pretty late in the cycle and this a rather old bug.
Nit: a Fіxes tag would have been nice.
prev parent reply other threads:[~2023-04-05 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 22:09 [PATCH 0/1] nvme-tcp: fence TCP socket on transport error Chris Leech
2023-03-20 22:09 ` [PATCH 1/1] " Chris Leech
2023-03-21 8:30 ` Sagi Grimberg
2023-03-21 16:30 ` Chris Leech
2023-03-21 16:30 ` [PATCH v2 1/1] nvme-tcp: fence TCP socket on receive error Chris Leech
2023-03-21 20:19 ` John Meneghini
2023-03-22 7:13 ` Sagi Grimberg
2023-04-05 15:21 ` Christoph Hellwig [this message]
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=ZC2SAy1YtT63JK8T@infradead.org \
--to=hch@infradead.org \
--cc=cleech@redhat.com \
--cc=jmeneghi@redhat.com \
--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