From: Bjorn Helgaas <helgaas@kernel.org>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [Patch v6 6/7] x86/PCI/ACPI: Use common interface to support PCI host bridge
Date: Wed, 7 Oct 2015 07:45:54 -0500 [thread overview]
Message-ID: <20151007124554.GA22797@localhost> (raw)
In-Reply-To: <5614DD67.4070801@linaro.org>
On Wed, Oct 07, 2015 at 04:52:55PM +0800, Hanjun Guo wrote:
> On 10/07/2015 02:01 AM, Bjorn Helgaas wrote:
> >On Mon, Sep 14, 2015 at 04:07:35PM +0800, Jiang Liu wrote:
> >>Use common interface to simplify ACPI PCI host bridge implementation.
> >>
> >>Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
> >>Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org>
> >
> >Is there a corresponding ia64 patch? If we're really consolidating
> >this code (which I completely support), we need to do the whole job.
>
> Yes, there is a patch for it:
>
> [Patch v6 7/7] ia64/PCI/ACPI: Use common interface to support PCI
> host bridge
>
> which has lots of code simplification [1],
>
> arch/ia64/pci/pci.c | 232
> ++++++++++-----------------------------------------
> 1 file changed, 46 insertions(+), 186 deletions(-)
>
> [1]: https://lkml.org/lkml/2015/9/14/84
Oh, sorry I missed that. I review things that appear on linux-pci,
and several patches in this series weren't posted there, so I didn't
see them.
Bjorn
next prev parent reply other threads:[~2015-10-07 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 8:07 [Patch v6 0/7] Consolidate ACPI PCI root common code into ACPI core Jiang Liu
2015-09-14 8:07 ` [Patch v6 1/7] ACPI/PCI: Enhance ACPI core to support sparse IO space Jiang Liu
2015-09-14 8:07 ` [Patch v6 2/7] ia64/PCI/ACPI: Use common ACPI resource parsing interface for host bridge Jiang Liu
2015-09-14 8:07 ` [Patch v6 3/7] ia64/PCI: Use common struct resource_entry to replace struct iospace_resource Jiang Liu
2015-09-14 8:07 ` [Patch v6 4/7] PCI/ACPI: Consolidate common PCI host bridge code into ACPI core Jiang Liu
2015-10-06 17:47 ` Bjorn Helgaas
2015-10-08 5:32 ` Jiang Liu
2015-10-08 13:20 ` Bjorn Helgaas
2015-10-09 8:19 ` Jiang Liu
2015-09-14 8:07 ` [Patch v6 5/7] ACPI, PCI: Reset acpi_root_dev->domain to 0 when pci_ignore_seg is set Jiang Liu
2015-10-06 17:54 ` Bjorn Helgaas
2015-09-14 8:07 ` [Patch v6 6/7] x86/PCI/ACPI: Use common interface to support PCI host bridge Jiang Liu
2015-10-06 18:01 ` Bjorn Helgaas
2015-10-07 8:52 ` Hanjun Guo
2015-10-07 12:45 ` Bjorn Helgaas [this message]
2015-09-14 8:07 ` [Patch v6 7/7] ia64/PCI/ACPI: " Jiang Liu
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=20151007124554.GA22797@localhost \
--to=helgaas@kernel.org \
--cc=Liviu.Dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=hpa@zytor.com \
--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=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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).