From: Jesse Barnes <jesse.barnes@intel.com>
To: alek du <alek.du@intel.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 1/3] pci: Add Intel SCH PCI IDs
Date: Wed, 23 Apr 2008 15:51:04 -0700 [thread overview]
Message-ID: <200804231551.05220.jesse.barnes@intel.com> (raw)
In-Reply-To: <20080422100140.71f947ca@dxy.sh.intel.com>
On Monday, April 21, 2008 7:01 pm alek du wrote:
> This patch adds Intel SCH chipsets (US15W, US15L, UL11L) PCI IDs, these IDs
> will be used by following SCH driver patches.
>
> Signed-off-by: Alek Du <alek.du@intel.com>
> ---
> include/linux/pci_ids.h | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
Alex, can any of these IDs be trimmed? We only want to bloat pci_ids.h with
the stuff that's actually used in several drivers. Other IDs can just be
defined directly in the driver in question...
Thanks,
Jesse
next prev parent reply other threads:[~2008-04-23 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 2:01 [PATCH 1/3] pci: Add Intel SCH PCI IDs alek du
2008-04-23 22:51 ` Jesse Barnes [this message]
2008-04-24 1:19 ` Alek Du
2008-04-24 1:47 ` Jesse Barnes
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=200804231551.05220.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=alek.du@intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@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