From: Olivier Galibert <galibert@pobox.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI mmconfig support for Intel 915 bridges
Date: Thu, 11 Jan 2007 15:38:15 +0100 [thread overview]
Message-ID: <20070111143815.GA3254@dspnet.fr.eu.org> (raw)
In-Reply-To: <200701101853.04059.jbarnes@virtuousgeek.org>
On Wed, Jan 10, 2007 at 06:53:03PM -0800, Jesse Barnes wrote:
> This is a resend of the patch I sent earlier to Oliver. It adds support
> for Intel 915 bridge chips to the new PCI MMConfig detection code. Tested
> and works on my sole 915 based platform (a Toshiba laptop). I added
> register masking per Oliver's suggestion, and moved the __init qualifier to
> after the 'static const char' to match Ogawa-san's recent cleanup patches.
>
> Over time we can probably associate more PCI IDs with this routine, since
> i915 family contains a few other chips. But since I didn't have platforms
> to test such additions on, they're left out for now.
>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Olivier Galibert <galibert@pobox.com>
Andrew, you sent me a series of emails to tell me the patches had
moved to another subsystem tree, can you tell me which one? There is
at least an anti-regression patch to add on top (the Asus/Nvidia
special case is causing oopses right now).
OG.
next prev parent reply other threads:[~2007-01-11 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 2:53 [PATCH] PCI mmconfig support for Intel 915 bridges Jesse Barnes
2007-01-11 14:38 ` Olivier Galibert [this message]
2007-04-25 22:35 ` Jesse Barnes
2007-04-25 23:07 ` Andrew Morton
2007-04-25 23:16 ` 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=20070111143815.GA3254@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=akpm@osdl.org \
--cc=jbarnes@virtuousgeek.org \
--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