stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
	sagi@grimberg.me, mb@lightnvm.io, linux-nvme@lists.infradead.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] nvme: fix lightnvm check
Date: Thu, 7 Sep 2017 14:01:28 +0200	[thread overview]
Message-ID: <20170907120128.GB18794@lst.de> (raw)
In-Reply-To: <20170906150604.GD17331@localhost.localdomain>

On Wed, Sep 06, 2017 at 11:06:04AM -0400, Keith Busch wrote:
> Ugh, even with this quirk, new lightnvm device will be broken for
> all existing kernels. This sort of thing really could benefit from a
> standard's defined capability or command set supported bit to distinguish
> lightnvm devices. Lacking that, this looks like the only thing we can
> do at the moment.

I told them to register a different class code for these devices a long
time ago, but nothing happened.  Then again I might underestimate the
complexity of getting a class code..

  reply	other threads:[~2017-09-07 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06  9:48 [PATCH] nvme: fix lightnvm check Christoph Hellwig
2017-09-06 10:22 ` Sagi Grimberg
2017-09-06 10:25 ` Sagi Grimberg
2017-09-06 15:06 ` Keith Busch
2017-09-07 12:01   ` Christoph Hellwig [this message]
2017-09-07 12:15     ` Matias Bjørling
2017-09-07 12:20       ` Christoph Hellwig
2017-09-07 12:34         ` Matias Bjørling
  -- strict thread matches above, loose matches on Subject: below --
2017-09-06  9:50 Christoph Hellwig

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=20170907120128.GB18794@lst.de \
    --to=hch@lst.de \
    --cc=keith.busch@intel.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mb@lightnvm.io \
    --cc=sagi@grimberg.me \
    --cc=stable@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).