linux-kernel - Re: [PATCH] pcie hotplug: Change link order of pciehp

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]

Date:	Tue, 27 Jan 2009 15:37:00 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, linux-pci@...r.kernel.org,
	kristen.c.accardi@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pcie hotplug: Change link order of pciehp

On Monday, January 26, 2009 6:18 pm Randy Dunlap wrote:
> Matthew Garrett wrote:
> > commit bf53d46d80486fa613dc345aba5d42a29368056d
> > Author: Matthew Garrett <mjg@...hat.com>
> > Date:   Tue Jan 27 11:29:02 2009 +1100
> >
> > pcie hotplug: Change link order of pciehp
> >
> > Some hardware exposes PCIE slots in such a way that they can be claimed
> > by either the acpiphp or pciehp driver. pciehp is the preferred driver if
> > the firmware allows the OS to claim control via the _OSC method so should
> > be loaded first - if it fails to bind (either due to a missing _OSC
> > method or the firmware refusing to hand off control) then we can fall
> > back to acpiphp or a vendor-specific driver.
> >
> > This patch simply changes the link order to ensure that pciehp will be
> > initialised before acpiphp if both are statically built into the kernel.
> >
> > Signed-off-by: Matthew Garrett <mjg@...hat.com>
>
> Acked-by: Randy Dunlap <randy.dunlap@...cle.com>

Ok, applied to my for-linus branch, since this is actually affecting users 
now.

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