linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tj@kernel.org (Tejun Heo)
Subject: detect and warn about ahci-remapped NVMe devices
Date: Mon, 5 Dec 2016 14:33:27 -0500	[thread overview]
Message-ID: <20161205193327.GB30331@mtj.duckdns.org> (raw)
In-Reply-To: <1480703463-17489-1-git-send-email-hch@lst.de>

Hello,

On Fri, Dec 02, 2016@07:31:00PM +0100, Christoph Hellwig wrote:
> Just a small band-aid to detect the AHCI-remapped NVMe devices
> for now.  Hopefully we'll eventually get a fake PCIe root port
> driver ala VMD for them.

Applied 1-3 to libata/for-4.10.  Fixed the dup constant definition in
0002.

Thanks.

-- 
tejun

      parent reply	other threads:[~2016-12-05 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 18:31 detect and warn about ahci-remapped NVMe devices Christoph Hellwig
2016-12-02 18:31 ` [PATCH 1/3] nvme: move NVMe class code to pci_ids.h Christoph Hellwig
2016-12-02 18:31 ` [PATCH 2/3] ahci-remap.h: add ahci remapping definitions Christoph Hellwig
2016-12-03 10:57   ` Sergei Shtylyov
2016-12-05 15:31     ` Christoph Hellwig
2016-12-02 18:31 ` [PATCH 3/3] ahci: warn about remapped NVMe devices Christoph Hellwig
2016-12-05 19:33 ` Tejun Heo [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=20161205193327.GB30331@mtj.duckdns.org \
    --to=tj@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).