From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, Tomasz Nowicki <tn@semihalf.com>,
Mark Salter <msalter@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] PCI: ACPI: IA64: fix IO port generic range check
Date: Mon, 1 Feb 2016 13:34:37 +0000 [thread overview]
Message-ID: <20160201133437.GD10764@red-moon> (raw)
In-Reply-To: <56AF4359.1020709@linaro.org>
On Mon, Feb 01, 2016 at 07:36:57PM +0800, Hanjun Guo wrote:
[...]
> >diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
> >index 3cd6983..e20dbe5 100644
> >--- a/arch/x86/pci/acpi.c
> >+++ b/arch/x86/pci/acpi.c
> >@@ -275,11 +275,14 @@ static void pci_acpi_root_release_info(struct acpi_pci_root_info *ci)
> > * to access PCI configuration space.
> > *
> > * So explicitly filter out PCI CFG IO ports[0xCF8-0xCFF].
> >+ *
> >+ * Furthermore, IO ports address space is limited to 16k on x86,
>
> Minor typo for '16k', should be '64k'? or we can just specify
> the magic number 0x10003?
Thanks, I will fix it, it is a leftover.
> By the way, I tested this patch both on x86 and ia64 box,
> and PCI for both box is working properly after boot,
>
> Tested-by: Hanjun Guo <hanjun.guo@linaro.org>
Thank you very much !
Lorenzo
next prev parent reply other threads:[~2016-02-01 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 10:25 [PATCH] PCI: ACPI: IA64: fix IO port generic range check Lorenzo Pieralisi
2016-02-01 11:36 ` Hanjun Guo
2016-02-01 13:34 ` Lorenzo Pieralisi [this message]
2016-02-09 14:57 ` Lorenzo Pieralisi
2016-02-09 14:57 ` Lorenzo Pieralisi
2016-02-09 17:00 ` Bjorn Helgaas
2016-02-09 18:11 ` Lorenzo Pieralisi
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=20160201133437.GD10764@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tn@semihalf.com \
--cc=tony.luck@intel.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.