From: Bjorn Helgaas <helgaas@kernel.org>
To: Adrian-Ken Rueegsegger <ken@codelabs.ch>
Cc: linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH] x86/PCI: Refine PCI support check in pcibios_init()
Date: Mon, 11 Apr 2016 23:47:29 -0500 [thread overview]
Message-ID: <20160412044729.GC11361@localhost> (raw)
In-Reply-To: <1458729269-9440-2-git-send-email-ken@codelabs.ch>
On Wed, Mar 23, 2016 at 11:34:29AM +0100, Adrian-Ken Rueegsegger wrote:
> Also consider raw_pci_ext_ops when validating if a system has PCI
> support. This leads to proper resource allocation via
> pcibios_resource_survey() in the case where PCI config space is
> exclusively accessed through MMCONFIG.
>
> Signed-off-by: Adrian-Ken Rueegsegger <ken@codelabs.ch>
Applied to pci/enumeration for v4.7, thanks!
> ---
> arch/x86/pci/common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c
> index 8fd6f44..50b123d 100644
> --- a/arch/x86/pci/common.c
> +++ b/arch/x86/pci/common.c
> @@ -517,7 +517,7 @@ void __init pcibios_set_cache_line_size(void)
>
> int __init pcibios_init(void)
> {
> - if (!raw_pci_ops) {
> + if (!raw_pci_ops && !raw_pci_ext_ops) {
> printk(KERN_WARNING "PCI: System does not support PCI\n");
> return 0;
> }
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-04-12 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 10:34 PCI support check in pcibios_init() Adrian-Ken Rueegsegger
2016-03-23 10:34 ` [RFC PATCH] x86/PCI: Refine " Adrian-Ken Rueegsegger
2016-04-12 4:47 ` Bjorn Helgaas [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=20160412044729.GC11361@localhost \
--to=helgaas@kernel.org \
--cc=ken@codelabs.ch \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).