linux-kernel - Re: [PATCH 0/3] ACPI/PCI Hotplug: acpiphp cleanup

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: <20090714122731.1ebea158@jbarnes-g45>
Date:	Tue, 14 Jul 2009 12:27:31 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Alex Chiang <achiang@...com>
Cc:	lenb@...nel.org, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH 0/3] ACPI/PCI Hotplug: acpiphp cleanup

On Fri, 10 Jul 2009 13:42:33 -0600
Alex Chiang <achiang@...com> wrote:

> Hi Len, Jesse,
> 
> I'd like to have this patch series considered for the current release
> because it clarifies some usage of the new interface
> acpi_get_pci_dev() that was also introduced in this release cycle.
> 
> The short story is, acpi_get_pci_dev() doesn't always return a struct
> pci_dev, because a PCI root bridge may not have an associated pci_dev
> on platforms with non-materialized root bridges.
> 
> See this patch for more:
> 
> 	http://patchwork.kernel.org/patch/32613/
> 
> I had to export acpi_pci_root to accomplish my goal, but it did result
> in a nice net cleanup in acpiphp.
> 
> It should probably go through Jesse's tree, but needs Len's ACK for
> the acpi_pci_root bit.

Haven't heard from Len yet, but I'm a bit nervous about adding this to
for-linus.  We already have a fix upstream for the acpi_get_pci_dev
issue right?  So there's no hurry on this set of (nice) cleanups is
there?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/