linux-kernel - Re: [PATCH] PCI mmconfig support for Intel 915 bridges

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070425160737.37e684cf.akpm@linux-foundation.org>
Date:	Wed, 25 Apr 2007 16:07:37 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jesse Barnes <jesse.barnes@...el.com>
Cc:	Olivier Galibert <galibert@...ox.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI mmconfig support for Intel 915 bridges

On Wed, 25 Apr 2007 15:35:15 -0700 Jesse Barnes <jesse.barnes@...el.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@...tuousgeek.org>
> >

Can we have a refresh, retest and resend please?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/