From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.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: Mon, 8 Feb 2016 12:01:16 +0200 [thread overview]
Message-ID: <56B8676C.20600@dev.mellanox.co.il> (raw)
In-Reply-To: <56B8448A.3000106@suse.de>
> Do we have defined sysfs attributes for NVMe devices nowadays?
/sys/block/nvme0n1/uuid
> If so I'd be willing to create/send some sysfs rules for them.
That'd be great!
next prev parent reply other threads:[~2016-02-08 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 18:33 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 [this message]
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
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=56B8676C.20600@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--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
Powered by JetHome