From: Andrew Morton <akpm@linux-foundation.org>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: Olivier Galibert <galibert@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI mmconfig support for Intel 915 bridges
Date: Wed, 25 Apr 2007 16:07:37 -0700 [thread overview]
Message-ID: <20070425160737.37e684cf.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704251535.17528.jesse.barnes@intel.com>
On Wed, 25 Apr 2007 15:35:15 -0700 Jesse Barnes <jesse.barnes@intel.com> wrote:
> I see the other mmconfig stuff is upstream now, can we get this added
> too? The Asus bug Olivier mentioned also appears to be fixed, so this
> patch should be safe.
>
> Thanks,
> Jesse
^^^^^ is an evil top-poster!
>
> On Wednesday, January 10, 2007 6:53 pm 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>
> >
Can we have a refresh, retest and resend please?
next prev parent reply other threads:[~2007-04-25 23:07 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
2007-04-25 22:35 ` Jesse Barnes
2007-04-25 23:07 ` Andrew Morton [this message]
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=20070425160737.37e684cf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=galibert@pobox.com \
--cc=jesse.barnes@intel.com \
--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