From: David Cohen <david.a.cohen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cjb@laptop.org, bhelgaas@google.com, adrian.hunter@intel.com,
wfp5p@virginia.edu, g.liakhovetski@gmx.de,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] pci_id: add Intel Merrifield mmc pci id
Date: Tue, 01 Oct 2013 13:14:46 -0700 [thread overview]
Message-ID: <524B2D36.3040803@linux.intel.com> (raw)
In-Reply-To: <20131001200755.GA28165@kroah.com>
On 10/01/2013 01:07 PM, Greg KH wrote:
> On Tue, Oct 01, 2013 at 01:00:32PM -0700, David Cohen wrote:
>> Signed-off-by: David Cohen <david.a.cohen@linux.intel.com>
>> ---
>> include/linux/pci_ids.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
>> index 97fbecd..2a89103 100644
>> --- a/include/linux/pci_ids.h
>> +++ b/include/linux/pci_ids.h
>> @@ -2551,6 +2551,7 @@
>> #define PCI_DEVICE_ID_INTEL_MFD_EMMC0 0x0823
>> #define PCI_DEVICE_ID_INTEL_MFD_EMMC1 0x0824
>> #define PCI_DEVICE_ID_INTEL_MRST_SD2 0x084F
>> +#define PCI_DEVICE_ID_INTEL_MRFL_MMC 0x1190
>
> Please read the top of this file for why you shouldn't be adding new
> device ids to it.
Thanks for the reply. I am sending new patch.
Br, David
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2013-10-01 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:00 [PATCH 1/2] pci_id: add Intel Merrifield mmc pci id David Cohen
2013-10-01 20:00 ` [PATCH 2/2] mmc: sdhci-pci: add Intel Merrifield support David Cohen
2013-10-01 20:07 ` [PATCH 1/2] pci_id: add Intel Merrifield mmc pci id Greg KH
2013-10-01 20:14 ` David Cohen [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=524B2D36.3040803@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=bhelgaas@google.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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).