netdev - Re: [PATCH v4 00/13] TCP transport binding for NVMe over Fabrics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7bfee670-1658-3888-fc00-3d8c1f4a369e@grimberg.me>
Date:   Fri, 30 Nov 2018 12:37:42 -0800
From:   Sagi Grimberg <sagi@...mberg.me>
To:     David Miller <davem@...emloft.net>
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


>>> 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>

Thanks Dave.