Re: please drop the nvme code from net-next

[PATCH] nvme: NVME_TCP_OFFLOAD should not default to m · Geert Uytterhoeven <geert+renesas@glider.be> · 2021-06-08
Re: [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m · Christoph Hellwig <hch@lst.de> · 2021-06-08
Re: [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m · Geert Uytterhoeven <geert@linux-m68k.org> · 2021-06-08
please drop the nvme code from net-next · Christoph Hellwig <hch@lst.de> · 2021-06-08
Re: please drop the nvme code from net-next · David Miller <davem@davemloft.net> · 2021-06-08
Re: please drop the nvme code from net-next · Keith Busch <kbusch@kernel.org> · 2021-06-08
Re: [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m · patchwork-bot+netdevbpf@kernel.org · 2021-06-08

From: Keith Busch <kbusch@kernel.org>
Date: 2021-06-08 19:41:14
Also in: linux-nvme, lkml

On Tue, Jun 08, 2021 at 12:08:39PM -0700, David Miller wrote:

From: Christoph Hellwig <hch@lst.de>
Date: Tue, 8 Jun 2021 15:43:03 +0200

quoted

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?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help