[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7f154bc-d9ab-bbc6-b85d-5a96034c552e@grimberg.me>
Date: Mon, 26 Nov 2018 23:45:01 -0800
From: Sagi Grimberg <sagi@...mberg.me>
To: Keith Busch <keith.busch@...el.com>
Cc: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH nvme-cli v3 15/13] nvme: Add TCP transport
> The cli parts good to me. Is there any forseeable issue if I apply these
> ahead of the kernel integration? I don't see any, but just want to
> confirm since its all in one series.
I don't see an issue, note that its on top of the sqflow patch [1]
that I've been meaning to ping you on.
[PATCH nvme-cli 5/4 v4] fabrics: support fabrics sq flow control disable
from series: Support SQ flow control disabled mode (TP 8005)
Powered by blists - more mailing lists