From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
linux-pci@vger.kernel.org, kristen.c.accardi@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pcie hotplug: Change link order of pciehp
Date: Tue, 27 Jan 2009 15:37:00 -0800 [thread overview]
Message-ID: <200901271537.00957.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <497E6EDA.2050700@oracle.com>
On Monday, January 26, 2009 6:18 pm Randy Dunlap wrote:
> Matthew Garrett wrote:
> > commit bf53d46d80486fa613dc345aba5d42a29368056d
> > Author: Matthew Garrett <mjg@redhat.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@redhat.com>
>
> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Ok, applied to my for-linus branch, since this is actually affecting users
now.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-01-27 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 0:37 [PATCH] pcie hotplug: Change link order of pciehp Matthew Garrett
2009-01-27 0:44 ` Randy Dunlap
2009-01-27 1:03 ` Matthew Garrett
2009-01-27 2:18 ` Randy Dunlap
2009-01-27 23:37 ` Jesse Barnes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901271537.00957.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.