[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210608194042.GA339628@dhcp-10-100-145-180.wdc.com>
Date: Tue, 8 Jun 2021 12:40:42 -0700
From: Keith Busch <kbusch@...nel.org>
To: David Miller <davem@...emloft.net>
Cc: hch@....de, geert@...ux-m68k.org, axboe@...com, sagi@...mberg.me,
okulkarni@...vell.com, hare@...e.de, dbalandin@...vell.com,
himanshu.madhani@...cle.com, smalin@...vell.com, pmladek@...e.com,
linux-nvme@...ts.infradead.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: please drop the nvme code from net-next
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?
Powered by blists - more mailing lists