From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
Subject: [PATCH 2/3] ahci-remap.h: add ahci remapping definitions
Date: Sat, 3 Dec 2016 13:57:01 +0300 [thread overview]
Message-ID: <aa6cba2c-6cf7-0222-b871-d98d1c8e4fe8@cogentembedded.com> (raw)
In-Reply-To: <1480703463-17489-3-git-send-email-hch@lst.de>
Hello.
On 12/2/2016 9:31 PM, Christoph Hellwig wrote:
> From: Dan Williams <dan.j.williams at intel.com>
>
> Signed-off-by: Dan Williams <dan.j.williams at intel.com>
> [hch: split into a separate header and commit]
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
> include/linux/ahci-remap.h | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 include/linux/ahci-remap.h
>
> diff --git a/include/linux/ahci-remap.h b/include/linux/ahci-remap.h
> new file mode 100644
> index 0000000..883d366
> --- /dev/null
> +++ b/include/linux/ahci-remap.h
> @@ -0,0 +1,29 @@
> +#ifndef _LINUX_AHCI_REMAP_H
> +#define _LINUX_AHCI_REMAP_H
> +
> +#include <linux/sizes.h>
> +
> +#define AHCI_VSCAP 0xa4
> +#define AHCI_REMAP_CAP 0x800
> +#define AHCI_VSCAP 0xa4
Why do it twice?
MBR, Sergei
next prev parent reply other threads:[~2016-12-03 10:57 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 [this message]
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 ` detect and warn about ahci-remapped " Tejun Heo
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=aa6cba2c-6cf7-0222-b871-d98d1c8e4fe8@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
/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).