linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jon Masters <jcm@jonmasters.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	rafael@kernel.org, linux-pci@vger.kernel.org,
	Will Deacon <will.deacon@arm.com>,
	okaya@codeaurora.org, wangyijing@huawei.com,
	Tomasz Nowicki <tn@semihalf.com>,
	linaro-acpi@lists.linaro.org,
	David Daney <ddaney@caviumnetworks.com>,
	linux-acpi@vger.kernel.org, robert.richter@caviumnetworks.com,
	Bjorn Helgaas <helgaas@kernel.org>,
	msalter@redhat.com, Arnd Bergmann <arnd@arndb.de>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Liviu.Dudau@arm.com, Marcin Wojtas <mw@semihalf.com>,
	linux-arm-kernel@lists.infradead.org,
	Jayachandran C <jchandra@broadcom.com>,
	linux-kernel@vger.kernel.org, Hanjun Guo <hanjun.guo@linaro.org>,
	Suravee.Suthikulpanit@amd.com, jiang.liu@linux.intel.com
Subject: Re: [PATCH v2 2/4] PCI: Provide common functions for ECAM mapping
Date: Thu, 14 Apr 2016 11:05:49 +0100	[thread overview]
Message-ID: <20160414100549.GC24733@red-moon> (raw)
In-Reply-To: <570F30D4.2030102@jonmasters.org>

On Thu, Apr 14, 2016 at 01:55:32AM -0400, Jon Masters wrote:

[...]

> > I will comment on the patches as soon as I have time to review
> > them, I certainly would like to understand what we have to do with the
> > rest of the code though (provided this series is good to go) see above.
> 
> Right. That's my reason for asking. I'd like to know who is driving (I
> believe that to be Lorenzo) and what the path forward is, and whether we
> need to get additional support from anyone else. There's a multi-vendor
> meeting in the morning where I'm going to summarize the current state of
> these patches and I would like to know (soon) what the plan is so that
> we can get everyone on deck to help out at least with testing (most have
> tested the previous set, but we need public acks happening).

Testing always helps, this code needs reviewing from PCI and ACPI
standpoints, what we can do is review this series and repost the whole
thing when we agree the ECAM refactoring this series is implementing
is the right way to go and it is a step in that direction, with no
generic MCFG support in the kernel ACPI PCI on ARM64 can't be
implemented so I would start from that.

Lorenzo

  reply	other threads:[~2016-04-14 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1460414707-19153-1-git-send-email-jchandra@broadcom.com>
     [not found] ` <1460414707-19153-3-git-send-email-jchandra@broadcom.com>
2016-04-12  0:24   ` [PATCH v2 2/4] PCI: Provide common functions for ECAM mapping David Daney
2016-04-12  4:26     ` Jon Masters
2016-04-12 16:44       ` Lorenzo Pieralisi
2016-04-14  5:55         ` Jon Masters
2016-04-14 10:05           ` Lorenzo Pieralisi [this message]
     [not found] ` <1460414707-19153-4-git-send-email-jchandra@broadcom.com>
2016-04-12  0:34   ` [PATCH v2 3/4] PCI: generic, thunder: update to use generic ECAM API David Daney
2016-04-14 14:15     ` Jayachandran C
     [not found] ` <1460414707-19153-5-git-send-email-jchandra@broadcom.com>
2016-04-12  1:38   ` [PATCH v2 4/4] ACPI: PCI: Add generic PCI host controller kbuild test robot
2016-04-14 15:53   ` Sinan Kaya
2016-04-14 15:58     ` Sinan Kaya

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=20160414100549.GC24733@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=hanjun.guo@linaro.org \
    --cc=helgaas@kernel.org \
    --cc=jchandra@broadcom.com \
    --cc=jcm@jonmasters.org \
    --cc=jiang.liu@linux.intel.com \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=mw@semihalf.com \
    --cc=okaya@codeaurora.org \
    --cc=rafael@kernel.org \
    --cc=robert.richter@caviumnetworks.com \
    --cc=tn@semihalf.com \
    --cc=wangyijing@huawei.com \
    --cc=will.deacon@arm.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 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).