From: Bjorn Helgaas <helgaas@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Wolfram Sang <wsa@the-dreams.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms@verge.net.au>,
linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Resend: PATCH v2 0/3] Fix rcar-pcie for arm64
Date: Wed, 25 Nov 2015 16:40:33 +0000 [thread overview]
Message-ID: <20151125164033.GA1380@localhost> (raw)
In-Reply-To: <1448465439-2132-1-git-send-email-phil.edworthy@renesas.com>
Hi Phil,
On Wed, Nov 25, 2015 at 03:30:36PM +0000, Phil Edworthy wrote:
> The first patches fixes the build problem
I'm trying to figure out if v4.4 has a build problem we need to fix.
If I understand correctly, "PCI: rcar: Convert to DT resource parsing
API" doesn't fix a build problem in the current tree; rather, it
removes a dependency on ARM so that we can build it on ARM64.
> , and the second patch reverts the
> patch that removed the driver from arm64 builds. The final patch add a compat
> string for the r8a7795 (arm64) device.
>
> Tested on arm Koelsch board, all ok.
>
> Tested on arm64 Salvator-X board using renesas-drivers-2015-10-27-v4.3-rc7 from
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git with PCI
> next merged.
> Apart from patches to add the PCIe clock and DT nodes, it also needs this fix:
> ("PCI: MSI: Only use the generic MSI layer when domain is hierarchical")
I assume you mean this one from Marc: https://lkml.org/lkml/2015/11/23/388
(Was that posted to linux-pci? I don't see it in patchwork or my
linux-pci archives, so I hadn't seen it yet.)
How exactly is that related to this series? If I merge these before
Marc's change, do we have a tree that builds for arm64 but doesn't
work?
What about the PCIe clock and DT changes you mention? Is there a
reason to keep them separate? Would it be feasible to include the DT
changes in the same patch as the driver change that uses those
changes?
Bjorn
> Resent with whole series marked as v2 and acks, etc added.
>
> Harunobu Kurokawa (1):
> PCI: pcie-rcar: Add support for R-Car H3.
>
> Phil Edworthy (2):
> PCI: rcar: Convert to DT resource parsing API
> Revert "PCI: rcar: Build pcie-rcar.c only on ARM"
>
> Documentation/devicetree/bindings/pci/rcar-pci.txt | 3 +-
> drivers/pci/host/Kconfig | 3 +-
> drivers/pci/host/pcie-rcar.c | 117 +++++++++++++--------
> 3 files changed, 77 insertions(+), 46 deletions(-)
>
> --
> 2.5.0
>
> --
> 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
next prev parent reply other threads:[~2015-11-25 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:30 [Resend: PATCH v2 0/3] Fix rcar-pcie for arm64 Phil Edworthy
2015-11-25 15:30 ` [PATCH v2 1/3] PCI: rcar: Convert to DT resource parsing API Phil Edworthy
2015-11-25 15:30 ` [PATCH v2 2/3] Revert "PCI: rcar: Build pcie-rcar.c only on ARM" Phil Edworthy
2015-11-25 15:30 ` [PATCH v2 3/3] PCI: pcie-rcar: Add support for R-Car H3 Phil Edworthy
2015-11-25 16:40 ` Bjorn Helgaas [this message]
2015-11-26 8:32 ` [Resend: PATCH v2 0/3] Fix rcar-pcie for arm64 Phil Edworthy
2015-12-09 16:59 ` Bjorn Helgaas
2015-12-10 4:27 ` Simon Horman
2015-12-10 18:12 ` Phil Edworthy
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=20151125164033.GA1380@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=phil.edworthy@renesas.com \
--cc=wsa@the-dreams.de \
/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).