linux-kernel - Re: [PATCH 0/3, v16] PCI, ACPI: Physical PCI slot objects

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] [day] [month] [year] [list]

Message-Id: <200806101439.51174.jbarnes@virtuousgeek.org>
Date:	Tue, 10 Jun 2008 14:39:50 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Alex Chiang <achiang@...com>
Cc:	greg@...ah.com, Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Matthew Wilcox <matthew@....cx>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kristen.c.accardi@...el.com, lenb@...nel.org, pbadari@...ibm.com,
	linux-pci@...r.kernel.org, pcihpd-discuss@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3, v16] PCI, ACPI: Physical PCI slot objects

On Tuesday, June 10, 2008 2:25 pm Alex Chiang wrote:
> Hi Greg, Jesse,
>
> This is v16 of the physical PCI slot series.
>
> It is based off of Jesse's linux-next branch in his PCI tree.
>
> Greg, Jesse, there might be an issue with
> 372fa8fa0a77c47c7bcfae0ccd14e0c5f97d17fe, which is in Stephen
> Rothwell's linux-next tree, but not in Jesse's. The correct fix
> would be for Greg to entirely drop the hunk that touches
> drivers/pci/hotplug/fakephp.c.
>
> Jesse said he'd like to see final ACKs from Kenji-san and
> Kristen, and then we'll be good to go for 2.6.27.

Ok, pushed these to my linux-next tree.  As usual, testing & more review 
appreciated.

Thanks,
Jesse
--
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/