What is the plan ahead here? I think the nvme code looks pretty reasonable now (I'll do another pass at nitpicking), but we need the networking stuff sorted out with at least ACKs, or a merge through the networking tree and then a shared branch we can pull in.
- [PATCH v4 09/13] nvme-fabrics: allow user passing data d... Sagi Grimberg
- [PATCH v4 02/13] datagram: open-code copy_page_to_iter Sagi Grimberg
- [PATCH v4 13/13] nvme-tcp: add NVMe over TCP host driver Sagi Grimberg
- [PATCH v4 11/13] nvmet-tcp: add NVMe over TCP target dri... Sagi Grimberg
- Re: [PATCH v4 11/13] nvmet-tcp: add NVMe over TCP t... Max Gurtovoy
- Re: [PATCH v4 11/13] nvmet-tcp: add NVMe over T... Sagi Grimberg
- [PATCH v4 12/13] nvmet: allow configfs tcp trtype config... Sagi Grimberg
- [PATCH v4 04/13] datagram: consolidate datagram copy to ... Sagi Grimberg
- [PATCH v4 03/13] iov_iter: pass void csum pointer to csu... Sagi Grimberg
- [PATCH v4 10/13] nvme-tcp: Add protocol header Sagi Grimberg
- Re: [PATCH v4 00/13] TCP transport binding for NVMe over... Christoph Hellwig
- Re: [PATCH v4 00/13] TCP transport binding for NVMe... Sagi Grimberg
- Re: [PATCH v4 00/13] TCP transport binding for ... David Miller
- Re: [PATCH v4 00/13] TCP transport binding ... Sagi Grimberg
