From: reg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Guo <peter.guo@bayhubtech.com>
Cc: Chris Ball <cjb@laptop.org>, Bjorn Helgaas <bhelgaas@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Bill Pemberton <wfp5p@virginia.edu>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Samuel Guan <samuel.guan@bayhubtech.com>
Subject: Re: [PATCH 1/2] mmc:sdhci-pci:Add O2Micor/BayHubTect PCI SD Host
Date: Tue, 24 Sep 2013 20:30:55 -0700 [thread overview]
Message-ID: <20130925033055.GA29234@kroah.com> (raw)
In-Reply-To: <9ac149a4448d4d99a280a37b104da1e3@BN1PR04MB091.namprd04.prod.outlook.com>
On Wed, Sep 25, 2013 at 03:20:07AM +0000, Peter Guo wrote:
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -1700,6 +1700,11 @@
> #define PCI_DEVICE_ID_O2_8221 0x8221
> #define PCI_DEVICE_ID_O2_8320 0x8320
> #define PCI_DEVICE_ID_O2_8321 0x8321
> +#define PCI_DEVICE_ID_O2_8520 0x8520
> +#define PCI_DEVICE_ID_O2_8420 0x8420
> +#define PCI_DEVICE_ID_O2_8421 0x8421
> +#define PCI_DEVICE_ID_O2_8620 0x8620
> +#define PCI_DEVICE_ID_O2_8621 0x8621
Please read the top of this file for why you shouldn't be adding new
device ids to it.
thanks,
greg k-h
next prev parent reply other threads:[~2013-09-25 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 3:20 [PATCH 1/2] mmc:sdhci-pci:Add O2Micor/BayHubTect PCI SD Host Peter Guo
2013-09-25 3:30 ` reg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-25 4:11 Peter Guo
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=20130925033055.GA29234@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=bhelgaas@google.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peter.guo@bayhubtech.com \
--cc=samuel.guan@bayhubtech.com \
--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 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.