From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] Remove the static list of PciChipset and construct it from SymTabRec instead.
Date: Sat, 07 May 2011 22:24:38 -0700 [thread overview]
Message-ID: <4DC62916.50803@whitecape.org> (raw)
In-Reply-To: <1304726935-8428-3-git-send-email-eric@anholt.net>
On 05/06/2011 05:08 PM, Eric Anholt wrote:
> This is one less place the new hardware enabler has to spam the
> chipset in. The PciChipset is just a match structure from PciId to
> the SymTabRec entry token, and our SymTabRec entry tokens are just the
> PciId, so it's trivial to construct.
> ---
> src/intel_module.c | 53 +++++++--------------------------------------------
> 1 files changed, 8 insertions(+), 45 deletions(-)
Acked-by: Kenneth Graunke <kenneth@whitecape.org>
I'm always glad to see lists of PCI IDs die.
next prev parent reply other threads:[~2011-05-08 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 0:08 [PATCH 1/4] Store the chipset info struct in the PCI match struct, instead of a switch() Eric Anholt
2011-05-07 0:08 ` [PATCH 2/4] Use the existing deviceID -> name mapping in SymTabRec instead of duping it Eric Anholt
2011-05-07 0:08 ` [PATCH 3/4] Remove the static list of PciChipset and construct it from SymTabRec instead Eric Anholt
2011-05-08 5:24 ` Kenneth Graunke [this message]
2011-05-07 0:08 ` [PATCH 4/4] Add support for Ivybridge chipset Eric Anholt
2011-05-07 20:17 ` Kenneth Graunke
2011-05-08 7:11 ` [PATCH 1/4] Store the chipset info struct in the PCI match struct, instead of a switch() Chris Wilson
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=4DC62916.50803@whitecape.org \
--to=kenneth@whitecape.org \
--cc=intel-gfx@lists.freedesktop.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