linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	linux-block@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional
Date: Tue, 9 Feb 2016 10:19:54 -0700	[thread overview]
Message-ID: <56BA1FBA.5080508@kernel.dk> (raw)
In-Reply-To: <20160209171911.GA30623@lst.de>

On 02/09/2016 10:19 AM, Christoph Hellwig wrote:
> Updated version below:
>
> ---
>  From d63251560cf2670badbc86c83502502f29c087e0 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Tue, 9 Feb 2016 18:11:32 +0100
> Subject: nvme: fix Kconfig description for BLK_DEV_NVME_SCSI
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   drivers/nvme/host/Kconfig | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
> index 59307f8..68fa858 100644
> --- a/drivers/nvme/host/Kconfig
> +++ b/drivers/nvme/host/Kconfig
> @@ -17,8 +17,9 @@ config BLK_DEV_NVME_SCSI
>   	  and block devices nodes, as well a a translation for a small
>   	  number of selected SCSI commands to NVMe commands to the NVMe
>   	  driver.  If you don't know what this means you probably want
> -	  to say N here, and if you know what it means you probably
> -	  want to say N as well.
> +	  to say N here, unless you run a distro that abuses the SCSI
> +	  emulation to provide stable device names for mount by id like
> +	  some OpenSuSE and SLES versions.

Thanks, looks good to me, I'll fold it in for the current series.

-- 
Jens Axboe

  reply	other threads:[~2016-02-09 17:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 18:33 complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional James Bottomley
2016-02-07  9:22 ` Christoph Hellwig
2016-02-07 16:04   ` James Bottomley
2016-02-07 22:28     ` Jens Axboe
2016-02-07 23:07       ` James Bottomley
2016-02-08  7:24         ` Christoph Hellwig
2016-02-08  7:32         ` Hannes Reinecke
2016-02-08 10:01           ` Sagi Grimberg
2016-02-08 10:13             ` Christoph Hellwig
2016-02-08 15:12               ` Keith Busch
2016-02-08 15:19                 ` Hannes Reinecke
2016-02-08 16:15                   ` Keith Busch
2016-02-08 15:23           ` James Bottomley
2016-02-09 12:50       ` Christoph Hellwig
2016-02-09 13:29         ` Jens Axboe
2016-02-09 17:12           ` Christoph Hellwig
2016-02-09 17:14             ` Jens Axboe
2016-02-09 17:19               ` Christoph Hellwig
2016-02-09 17:19                 ` Jens Axboe [this message]
2016-02-09 15:37         ` James Bottomley
2016-02-08  7:26     ` Hannes Reinecke

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=56BA1FBA.5080508@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).