All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David S . Miller" <davem@davemloft.net>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
	Sagi Grimberg <sagi@grimberg.me>,
	Omkar Kulkarni <okulkarni@marvell.com>,
	Hannes Reinecke <hare@suse.de>,
	Dean Balandin <dbalandin@marvell.com>,
	Himanshu Madhani <himanshu.madhani@oracle.com>,
	Shai Malin <smalin@marvell.com>, Petr Mladek <pmladek@suse.com>,
	linux-nvme@lists.infradead.org, netdev <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: please drop the nvme code from net-next
Date: Tue, 8 Jun 2021 15:43:03 +0200	[thread overview]
Message-ID: <20210608134303.GA30977@lst.de> (raw)
In-Reply-To: <CAMuHMdWgLf8GJfOaRUyx=AvOTnuOs8FS-2=C+OCk02OLDCyrDg@mail.gmail.com>

Hi Dave,

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.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David S . Miller" <davem@davemloft.net>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
	Sagi Grimberg <sagi@grimberg.me>,
	Omkar Kulkarni <okulkarni@marvell.com>,
	Hannes Reinecke <hare@suse.de>,
	Dean Balandin <dbalandin@marvell.com>,
	Himanshu Madhani <himanshu.madhani@oracle.com>,
	Shai Malin <smalin@marvell.com>, Petr Mladek <pmladek@suse.com>,
	linux-nvme@lists.infradead.org, netdev <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: please drop the nvme code from net-next
Date: Tue, 8 Jun 2021 15:43:03 +0200	[thread overview]
Message-ID: <20210608134303.GA30977@lst.de> (raw)
In-Reply-To: <CAMuHMdWgLf8GJfOaRUyx=AvOTnuOs8FS-2=C+OCk02OLDCyrDg@mail.gmail.com>

Hi Dave,

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.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-06-08 13:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 10:56 [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m Geert Uytterhoeven
2021-06-08 10:56 ` Geert Uytterhoeven
2021-06-08 12:19 ` Christoph Hellwig
2021-06-08 12:19   ` Christoph Hellwig
2021-06-08 13:37   ` Geert Uytterhoeven
2021-06-08 13:37     ` Geert Uytterhoeven
2021-06-08 13:43     ` Christoph Hellwig [this message]
2021-06-08 13:43       ` please drop the nvme code from net-next Christoph Hellwig
2021-06-08 19:08       ` David Miller
2021-06-08 19:08         ` David Miller
2021-06-08 19:40         ` Keith Busch
2021-06-08 19:40           ` Keith Busch
2021-06-08 19:10 ` [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m patchwork-bot+netdevbpf
2021-06-08 19:10   ` patchwork-bot+netdevbpf
2021-06-08 15:56 please drop the nvme code from net-next Shai Malin
2021-06-08 15:56 ` Shai Malin
2021-06-08 19:51 Shai Malin
2021-06-08 19:51 ` Shai Malin
2021-06-09 12:13 ` Shai Malin
2021-06-09 12:13   ` Shai Malin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210608134303.GA30977@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=davem@davemloft.net \
    --cc=dbalandin@marvell.com \
    --cc=geert@linux-m68k.org \
    --cc=hare@suse.de \
    --cc=himanshu.madhani@oracle.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=okulkarni@marvell.com \
    --cc=pmladek@suse.com \
    --cc=sagi@grimberg.me \
    --cc=smalin@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.