netdev - Re: please drop the nvme code from net-next

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-next>] [day] [month] [year] [list]

Message-ID: <SJ0PR18MB3882C20793EA35A3E8DAE300CC379@SJ0PR18MB3882.namprd18.prod.outlook.com>
Date:   Tue, 8 Jun 2021 19:51:25 +0000
From:   Shai Malin <smalin@...vell.com>
To:     Keith Busch <kbusch@...nel.org>, David Miller <davem@...emloft.net>
CC:     "hch@....de" <hch@....de>,
        "geert@...ux-m68k.org" <geert@...ux-m68k.org>,
        "axboe@...com" <axboe@...com>,
        "sagi@...mberg.me" <sagi@...mberg.me>,
        Omkar Kulkarni <okulkarni@...vell.com>,
        "hare@...e.de" <hare@...e.de>,
        Dean Balandin <dbalandin@...vell.com>,
        "himanshu.madhani@...cle.com" <himanshu.madhani@...cle.com>,
        "pmladek@...e.com" <pmladek@...e.com>,
        "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "malin1024@...il.com" <malin1024@...il.com>
Subject: Re: please drop the nvme code from net-next


On Tue, Jun 08, 2021 at 10:41:00PM -0700, Keith Busch wrote:
> On Tue, Jun 08, 2021 at 12:08:39PM -0700, David Miller wrote:
> > From: Christoph Hellwig <hch@....de>
> > Date: Tue, 8 Jun 2021 15:43:03 +0200
> >
> > > please drop the nvme-offload code from net-next.  Code for drivers/nvme/
> > > needs ACKs from us nvme maintainers and for something this significant
> > > also needs to go through the NVMe tree.  And this code is not ready yet.
> >
> > Please send me a revert, and I will apply it, thank you.
> >
> > It's tricky because at least one driver uses the new interfaces.
> 
> Shouldn't whoever merged un-ACK'ed patches from a different subsystem
> get to own the tricky revert?

Dave, we will provide a revert patch.