From: Bjorn Helgaas <bhelgaas@google.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: tegra: Do not build on 64-bit ARM
Date: Thu, 13 Nov 2014 12:04:48 -0700 [thread overview]
Message-ID: <20141113190448.GA14500@google.com> (raw)
In-Reply-To: <1415800418-22957-1-git-send-email-thierry.reding@gmail.com>
On Wed, Nov 12, 2014 at 02:53:37PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> 32-bit and 64-bit ARM use very different infrastructure to register a
> PCI host bridge. The Tegra PCIe host controller driver currently only
> supports the 32-bit ARM infrastructure, so prevent it from being built
> on 64-bit ARM where it will break.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
I applied both of these to pci/host-tegra for v3.19, thanks!
> ---
> drivers/pci/host/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig
> index 3dc25fad490c..9c56137e5e5e 100644
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> @@ -32,7 +32,7 @@ config PCI_IMX6
>
> config PCI_TEGRA
> bool "NVIDIA Tegra PCIe controller"
> - depends on ARCH_TEGRA
> + depends on ARCH_TEGRA && !ARM64
>
> config PCI_RCAR_GEN2
> bool "Renesas R-Car Gen2 Internal PCI controller"
> --
> 2.1.3
>
prev parent reply other threads:[~2014-11-13 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 13:53 [PATCH 1/2] PCI: tegra: Do not build on 64-bit ARM Thierry Reding
2014-11-12 13:53 ` [PATCH 2/2] PCI: tegra: Add Kconfig help text Thierry Reding
2014-11-13 19:04 ` 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=20141113190448.GA14500@google.com \
--to=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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).