From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Seth Heasley <seth.heasley@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
khali@linux-fr.org, x86@vger.kernel.org
Subject: Re: [PATCH 2.6.29-rc2] irq: irq and pci_ids patch for Intel Tigerpoint DeviceIDs
Date: Tue, 27 Jan 2009 09:49:07 -0800 [thread overview]
Message-ID: <200901270949.08211.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200901231243.38626.seth.heasley@intel.com>
On Friday, January 23, 2009 12:43 pm Seth Heasley wrote:
> This patch adds the Intel Tigerpoint LPC Controller DeviceIDs.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
Applied this one to my for-linus branch. Shouldn't hurt to add a new bridge
ID for 2.6.29.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-01-27 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 20:43 [PATCH 2.6.29-rc2] irq: irq and pci_ids patch for Intel Tigerpoint DeviceIDs Seth Heasley
2009-01-27 17:49 ` Jesse Barnes [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=200901270949.08211.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@intel.com \
--cc=x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox