From: Christoph Hellwig <hch@lst•de>
To: Geliang Tang <geliang@kernel•org>
Cc: Keith Busch <kbusch@kernel•org>, Jens Axboe <axboe@kernel•dk>,
Christoph Hellwig <hch@lst•de>, Sagi Grimberg <sagi@grimberg•me>,
Chaitanya Kulkarni <kch@nvidia•com>,
Matthieu Baerts <matttbe@kernel•org>,
Mat Martineau <martineau@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Simon Horman <horms@kernel•org>, Shuah Khan <shuah@kernel•org>,
Geliang Tang <tanggeliang@kylinos•cn>,
linux-nvme@lists•infradead.org, netdev@vger•kernel.org,
mptcp@lists•linux.dev, linux-kselftest@vger•kernel.org,
Hannes Reinecke <hare@suse•de>,
John Meneghini <jmeneghi@redhat•com>,
Randy Jennings <randyj@purestorage•com>,
Nilay Shroff <nilay@linux•ibm.com>,
zhenwei pi <zhenwei.pi@linux•dev>, Hui Zhu <zhuhui@kylinos•cn>,
Gang Yan <yangang@kylinos•cn>
Subject: Re: [PATCH 00/11] NVMe over MPTCP
Date: Thu, 28 May 2026 10:42:10 +0200 [thread overview]
Message-ID: <20260528084210.GA8141@lst.de> (raw)
In-Reply-To: <cover.1779934709.git.tanggeliang@kylinos.cn>
You need to talk to the NVMe technical working group, not us.
next prev parent reply other threads:[~2026-05-28 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 3:10 [PATCH 00/11] NVMe over MPTCP Geliang Tang
2026-05-28 3:10 ` [PATCH 01/11] nvmet-tcp: define accept tcp_proto struct Geliang Tang
2026-05-28 3:10 ` [PATCH 02/11] nvmet-tcp: implement accept mptcp proto Geliang Tang
2026-05-28 15:23 ` Jakub Kicinski
2026-05-29 14:20 ` Geliang Tang
2026-05-31 14:56 ` Nilay Shroff
2026-05-28 3:10 ` [PATCH 03/11] nvmet-tcp: define listen socket ops Geliang Tang
2026-05-28 3:10 ` [PATCH 04/11] nvmet-tcp: register target mptcp transport Geliang Tang
2026-05-28 3:10 ` [PATCH 05/11] nvmet-tcp: implement mptcp listen socket ops Geliang Tang
2026-05-31 15:01 ` Nilay Shroff
2026-05-28 3:10 ` [PATCH 06/11] nvme-fabrics: compare transport in ip_options_match Geliang Tang
2026-05-28 3:10 ` [PATCH 07/11] nvme-tcp: define host tcp_proto struct Geliang Tang
2026-05-28 3:10 ` [PATCH 08/11] nvme-tcp: register host mptcp transport Geliang Tang
2026-05-28 3:10 ` [PATCH 09/11] nvme-tcp: implement host mptcp proto Geliang Tang
2026-05-31 15:08 ` Nilay Shroff
2026-05-28 3:10 ` [PATCH 10/11] selftests: mptcp: add nvme over mptcp test Geliang Tang
2026-05-28 3:10 ` [PATCH 11/11] selftests: mptcp: nvme: add iopolicy tests Geliang Tang
2026-05-31 14:04 ` Nilay Shroff
2026-05-31 14:50 ` Nilay Shroff
2026-05-28 8:42 ` Christoph Hellwig [this message]
2026-05-29 14:31 ` [PATCH 00/11] NVMe over MPTCP Geliang Tang
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=20260528084210.GA8141@lst.de \
--to=hch@lst$(echo .)de \
--cc=axboe@kernel$(echo .)dk \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=geliang@kernel$(echo .)org \
--cc=hare@suse$(echo .)de \
--cc=horms@kernel$(echo .)org \
--cc=jmeneghi@redhat$(echo .)com \
--cc=kbusch@kernel$(echo .)org \
--cc=kch@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-nvme@lists$(echo .)infradead.org \
--cc=martineau@kernel$(echo .)org \
--cc=matttbe@kernel$(echo .)org \
--cc=mptcp@lists$(echo .)linux.dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nilay@linux$(echo .)ibm.com \
--cc=pabeni@redhat$(echo .)com \
--cc=randyj@purestorage$(echo .)com \
--cc=sagi@grimberg$(echo .)me \
--cc=shuah@kernel$(echo .)org \
--cc=tanggeliang@kylinos$(echo .)cn \
--cc=yangang@kylinos$(echo .)cn \
--cc=zhenwei.pi@linux$(echo .)dev \
--cc=zhuhui@kylinos$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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