From: Christoph Hellwig <hch@lst.de>
To: Caleb Sander <csander@purestorage.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Arnd Bergmann <arnd@arndb.de>,
linux-nvme@lists.infradead.org, linux-m68k@lists.linux-m68k.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec
Date: Wed, 22 Mar 2023 09:20:46 +0100 [thread overview]
Message-ID: <20230322082046.GC22321@lst.de> (raw)
In-Reply-To: <20230320155736.1492682-1-csander@purestorage.com>
Thanks,
applied to nvme-6.3.
prev parent reply other threads:[~2023-03-22 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 15:57 [PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec Caleb Sander
2023-03-20 18:59 ` Sagi Grimberg
2023-03-22 8:20 ` 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=20230322082046.GC22321@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=axboe@fb.com \
--cc=csander@purestorage.com \
--cc=geert@linux-m68k.org \
--cc=kbusch@kernel.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).