From: Greg KH <greg@kroah.com>
To: Seth Heasley <seth.heasley@intel.com>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, james.d.ralston@intel.com
Subject: Re: [PATCH 6/6] pci: irq and pci_ids patch for Intel Lynx Point DeviceIDs
Date: Mon, 23 Jan 2012 17:14:30 -0800 [thread overview]
Message-ID: <20120124011430.GA13171@kroah.com> (raw)
In-Reply-To: <201201231646.24194.seth.heasley@intel.com>
On Mon, Jan 23, 2012 at 04:46:24PM -0800, Seth Heasley wrote:
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2800,6 +2800,8 @@
> #define PCI_DEVICE_ID_INTEL_82454NX 0x84cb
> #define PCI_DEVICE_ID_INTEL_84460GX 0x84ea
> #define PCI_DEVICE_ID_INTEL_IXP4XX 0x8500
> +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MIN 0x8c40
> +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MAX 0x8c5f
You forgot to read the top of this file.
next prev parent reply other threads:[~2012-01-24 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 0:46 [PATCH 6/6] pci: irq and pci_ids patch for Intel Lynx Point DeviceIDs Seth Heasley
2012-01-24 1:14 ` Greg KH [this message]
2012-01-27 18:31 ` Jesse Barnes
2012-01-27 18:56 ` Heasley, Seth
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=20120124011430.GA13171@kroah.com \
--to=greg@kroah.com \
--cc=james.d.ralston@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@intel.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