All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Christoph Hellwig <hch@lst.de>,
	tj@kernel.org, dan.j.williams@intel.com,
	linux-ide@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/3] ahci-remap.h: add ahci remapping definitions
Date: Mon, 5 Dec 2016 16:31:32 +0100	[thread overview]
Message-ID: <20161205153132.GC6340@lst.de> (raw)
In-Reply-To: <aa6cba2c-6cf7-0222-b871-d98d1c8e4fe8@cogentembedded.com>

On Sat, Dec 03, 2016 at 01:57:01PM +0300, Sergei Shtylyov wrote:
>> +#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?

No good reason, probably just me messing up the move..

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/3] ahci-remap.h: add ahci remapping definitions
Date: Mon, 5 Dec 2016 16:31:32 +0100	[thread overview]
Message-ID: <20161205153132.GC6340@lst.de> (raw)
In-Reply-To: <aa6cba2c-6cf7-0222-b871-d98d1c8e4fe8@cogentembedded.com>

On Sat, Dec 03, 2016@01:57:01PM +0300, Sergei Shtylyov wrote:
>> +#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?

No good reason, probably just me messing up the move..

  reply	other threads:[~2016-12-05 15:32 UTC|newest]

Thread overview: 14+ 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 ` 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   ` Christoph Hellwig
2016-12-02 18:31 ` [PATCH 2/3] ahci-remap.h: add ahci remapping definitions Christoph Hellwig
2016-12-02 18:31   ` Christoph Hellwig
2016-12-03 10:57   ` Sergei Shtylyov
2016-12-03 10:57     ` Sergei Shtylyov
2016-12-05 15:31     ` Christoph Hellwig [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-02 18:31   ` Christoph Hellwig
2016-12-05 19:33 ` detect and warn about ahci-remapped " Tejun Heo
2016-12-05 19:33   ` 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=20161205153132.GC6340@lst.de \
    --to=hch@lst.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=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 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.