[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181129.181403.1046644111319738364.davem@davemloft.net>
Date: Thu, 29 Nov 2018 18:14:03 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: sagi@...mberg.me
Cc: hch@....de, linux-nvme@...ts.infradead.org,
linux-block@...r.kernel.org, netdev@...r.kernel.org,
keith.busch@...el.com
Subject: Re: [PATCH v4 00/13] TCP transport binding for NVMe over Fabrics
From: Sagi Grimberg <sagi@...mberg.me>
Date: Thu, 29 Nov 2018 17:24:09 -0800
>
>> 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.
>
> I would think that having Dave ack patches 1-3 and taking it via the
> nvme tree should be easier..
>
> Dave? What would you prefer?
No preference, if the nvme tree makes things easier for you then
please do it that way.
Acked-by: David S. Miller <davem@...emloft.net>
Powered by blists - more mailing lists