From: Sagi Grimberg <sagi@grimberg.me>
To: Shai Malin <smalin@marvell.com>,
linux-nvme@lists.infradead.org, Erik.Smith@dell.com,
Douglas.Farley@dell.com, liuw@vmware.com
Cc: aelior@marvell.com, agershberg@marvell.com,
mkalderon@marvell.com, nassa@marvell.com, dbalandin@marvell.com,
malin1024@gmail.com
Subject: Re: [PATCH 0/7] RFC patch series - NVMeTCP Offload ULP
Date: Wed, 25 Nov 2020 17:26:45 -0800 [thread overview]
Message-ID: <eb819457-aee9-e203-13d6-72b3afa4cfff@grimberg.me> (raw)
In-Reply-To: <20201119142107.17429-1-smalin@marvell.com>
You should tag this set with RFC, this is not in consideration
for inclusion...
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-11-26 1:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:21 [PATCH 0/7] RFC patch series - NVMeTCP Offload ULP Shai Malin
2020-11-19 14:21 ` [PATCH 1/7] nvme-tcp-offload: Add nvme-tcp-offload - NVMeTCP HW offload ULP Shai Malin
2020-11-26 1:22 ` Sagi Grimberg
2020-11-26 1:55 ` Sagi Grimberg
2020-12-01 22:38 ` [EXT] " Shai Malin
2020-11-19 14:21 ` [PATCH 2/7] nvme-fabrics: Move NVMF_ALLOWED_OPTS and NVMF_REQUIRED_OPTS definitions Shai Malin
2020-11-26 1:27 ` Sagi Grimberg
2020-11-19 14:21 ` [PATCH 3/7] nvme-tcp-offload: Add device scan implementation Shai Malin
2020-11-19 14:21 ` [PATCH 4/7] nvme-tcp-offload: Add controller level implementation Shai Malin
2020-11-19 14:21 ` [PATCH 5/7] nvme-tcp-offload: Add controller level error recovery implementation Shai Malin
2020-11-19 14:21 ` [PATCH 6/7] nvme-tcp-offload: Add queue level implementation Shai Malin
2020-11-19 14:21 ` [PATCH 7/7] nvme-tcp-offload: Add IO " Shai Malin
2020-11-24 10:41 ` [PATCH 0/7] RFC patch series - NVMeTCP Offload ULP Max Gurtovoy
2020-11-26 1:26 ` Sagi Grimberg [this message]
2020-12-01 22:21 ` [EXT] " Shai Malin
[not found] <PH0PR18MB38457E1674A23D869414FECACCFA0@PH0PR18MB3845.namprd18.prod.outlook.com>
2020-11-26 1:19 ` Sagi Grimberg
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=eb819457-aee9-e203-13d6-72b3afa4cfff@grimberg.me \
--to=sagi@grimberg.me \
--cc=Douglas.Farley@dell.com \
--cc=Erik.Smith@dell.com \
--cc=aelior@marvell.com \
--cc=agershberg@marvell.com \
--cc=dbalandin@marvell.com \
--cc=linux-nvme@lists.infradead.org \
--cc=liuw@vmware.com \
--cc=malin1024@gmail.com \
--cc=mkalderon@marvell.com \
--cc=nassa@marvell.com \
--cc=smalin@marvell.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.