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]

Date:	Thu, 11 Jan 2007 15:38:15 +0100
From:	Olivier Galibert <galibert@...ox.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI mmconfig support for Intel 915 bridges

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@...tuousgeek.org>

Signed-off-by: Olivier Galibert <galibert@...ox.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.

-
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/