From: Denis Turischev <denis@compulab.co.il>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
David Brownell <dbrownell@users.sourceforge.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: [PATCH 1/3] pci_ids: add Intel Tunnel Creek LPC Bridge device ID.
Date: Sun, 13 Mar 2011 17:26:40 +0200 [thread overview]
Message-ID: <4D7CE230.1070004@compulab.co.il> (raw)
Signed-off-by: Denis Turischev <denis@compulab.co.il>
---
include/linux/pci_ids.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 3adb06e..43779f9 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -2731,6 +2731,7 @@
#define PCI_DEVICE_ID_INTEL_82372FB_1 0x7601
#define PCI_DEVICE_ID_INTEL_SCH_LPC 0x8119
#define PCI_DEVICE_ID_INTEL_SCH_IDE 0x811a
+#define PCI_DEVICE_ID_INTEL_ITC_LPC 0x8186
#define PCI_DEVICE_ID_INTEL_82454GX 0x84c4
#define PCI_DEVICE_ID_INTEL_82450GX 0x84c5
#define PCI_DEVICE_ID_INTEL_82451NX 0x84ca
--
1.7.0.4
next reply other threads:[~2011-03-13 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 15:26 Denis Turischev [this message]
2011-03-13 15:28 ` [PATCH 2/3] lpc_sch: expand for Tunnel Creek Denis Turischev
2011-03-13 15:30 ` [PATCH 3/3] sch_gpio: expand for Tunnel Creak Denis Turischev
2011-03-14 10:53 ` [PATCH 3/3 v2] sch_gpio: expand for Tunnel Creek Denis Turischev
2011-03-14 11:45 ` Samuel Ortiz
2011-03-14 19:20 ` Grant Likely
2011-03-17 23:13 ` [PATCH 3/3] sch_gpio: expand for Tunnel Creak Samuel Ortiz
2011-03-17 23:12 ` [PATCH 2/3] lpc_sch: expand for Tunnel Creek Samuel Ortiz
2011-03-14 11:43 ` [PATCH 1/3] pci_ids: add Intel Tunnel Creek LPC Bridge device ID Samuel Ortiz
2011-03-14 15:50 ` Jesse Barnes
2011-03-17 23:11 ` Samuel Ortiz
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=4D7CE230.1070004@compulab.co.il \
--to=denis@compulab.co.il \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.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 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.