From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: "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, 09 Feb 2016 07:37:37 -0800 [thread overview]
Message-ID: <1455032257.2340.1.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160209125011.GC25353@lst.de>
On Tue, 2016-02-09 at 13:50 +0100, Christoph Hellwig wrote:
> Jens,
>
> do you want a 'default y' patch or just a better description? I'd be
> happy to send either one.
Since it only appears to be SUSE and they've now been told, better
description is fine.
James
WARNING: multiple messages have this Message-ID (diff)
From: James.Bottomley@HansenPartnership.com (James Bottomley)
Subject: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional
Date: Tue, 09 Feb 2016 07:37:37 -0800 [thread overview]
Message-ID: <1455032257.2340.1.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160209125011.GC25353@lst.de>
On Tue, 2016-02-09@13:50 +0100, Christoph Hellwig wrote:
> Jens,
>
> do you want a 'default y' patch or just a better description? I'd be
> happy to send either one.
Since it only appears to be SUSE and they've now been told, better
description is fine.
James
next prev parent reply other threads:[~2016-02-09 15:37 UTC|newest]
Thread overview: 43+ 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-06 18:33 ` James Bottomley
2016-02-07 9:22 ` Christoph Hellwig
2016-02-07 9:22 ` Christoph Hellwig
2016-02-07 16:04 ` James Bottomley
2016-02-07 16:04 ` James Bottomley
2016-02-07 22:28 ` Jens Axboe
2016-02-07 22:28 ` Jens Axboe
2016-02-07 23:07 ` James Bottomley
2016-02-07 23:07 ` James Bottomley
2016-02-08 7:24 ` Christoph Hellwig
2016-02-08 7:24 ` Christoph Hellwig
2016-02-08 7:32 ` Hannes Reinecke
2016-02-08 7:32 ` Hannes Reinecke
2016-02-08 10:01 ` Sagi Grimberg
2016-02-08 10:01 ` Sagi Grimberg
2016-02-08 10:13 ` Christoph Hellwig
2016-02-08 10:13 ` Christoph Hellwig
2016-02-08 15:12 ` Keith Busch
2016-02-08 15:12 ` Keith Busch
2016-02-08 15:19 ` Hannes Reinecke
2016-02-08 15:19 ` Hannes Reinecke
2016-02-08 16:15 ` Keith Busch
2016-02-08 16:15 ` Keith Busch
2016-02-08 15:23 ` James Bottomley
2016-02-08 15:23 ` James Bottomley
2016-02-09 12:50 ` Christoph Hellwig
2016-02-09 12:50 ` Christoph Hellwig
2016-02-09 13:29 ` Jens Axboe
2016-02-09 13:29 ` Jens Axboe
2016-02-09 17:12 ` Christoph Hellwig
2016-02-09 17:12 ` Christoph Hellwig
2016-02-09 17:14 ` Jens Axboe
2016-02-09 17:14 ` Jens Axboe
2016-02-09 17:19 ` Christoph Hellwig
2016-02-09 17:19 ` Christoph Hellwig
2016-02-09 17:19 ` Jens Axboe
2016-02-09 17:19 ` Jens Axboe
2016-02-09 15:37 ` James Bottomley [this message]
2016-02-09 15:37 ` James Bottomley
2016-02-08 7:26 ` Hannes Reinecke
2016-02-08 7:26 ` Hannes Reinecke
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=1455032257.2340.1.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--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 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.