From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 4/4] nvme: make SG_IO support optional
Date: Mon, 4 Jan 2016 17:41:17 +0100 [thread overview]
Message-ID: <20160104164117.GB17409@lst.de> (raw)
In-Reply-To: <20160104151925.GG31375@localhost.localdomain>
On Mon, Jan 04, 2016@03:19:25PM +0000, Keith Busch wrote:
> On Thu, Dec 24, 2015@03:27:02PM +0100, Christoph Hellwig wrote:
> > +config BLK_DEV_NVME_SCSI
> > + bool "SCSI emulation for NVMe device nodes"
> > + depends on BLK_DEV_NVME
>
> Can we make this "default y"? I strongly advocate for native NVMe over
> SCSI translations too, but I know of users relying on this. It's been
> built in for years and not aware of it breaking anything, so think it
> should be opt-out.
I'd really prefer not having to carry it around. But if any actual
breakage shows I'd be happy to default it to y ASAP.
prev parent reply other threads:[~2016-01-04 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 14:26 namespace list locking and ioctl fixes V2 Christoph Hellwig
2015-12-24 14:26 ` [PATCH 1/4] nvme: Move nvme_freeze/unfreeze_queues to nvme core Christoph Hellwig
2016-01-04 15:11 ` Keith Busch
2015-12-24 14:27 ` [PATCH 2/4] nvme: synchronize access to ctrl->namespaces Christoph Hellwig
2016-01-04 15:10 ` Keith Busch
2015-12-24 14:27 ` [PATCH 3/4] nvme: fixes for NVME_IOCTL_IO_CMD on the char device Christoph Hellwig
2016-01-04 15:08 ` Keith Busch
2015-12-24 14:27 ` [PATCH 4/4] nvme: make SG_IO support optional Christoph Hellwig
2016-01-03 16:36 ` Sagi Grimberg
2016-01-04 15:19 ` Keith Busch
2016-01-04 16:41 ` Christoph Hellwig [this message]
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=20160104164117.GB17409@lst.de \
--to=hch@lst.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox