public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail•com>
To: Bjorn Helgaas <bhelgaas@google•com>
Cc: Jason Cooper <jason@lakedaemon•net>, Andrew Lunn <andrew@lunn•ch>,
	Gregory Clement <gregory.clement@free-electrons•com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail•com>,
	linux-pci@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
	linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
Date: Thu, 18 Feb 2016 14:32:10 +0100	[thread overview]
Message-ID: <1455802330-17565-1-git-send-email-thierry.reding@gmail.com> (raw)

From: Thierry Reding <treding@nvidia•com>

This driver uses PCI glue that is only available on 32-bit ARM. This
used to work fine as long as ARCH_MVEBU and ARCH_DOVE were exclusively
32-bit, but that's changed now, with ARCH_MVEBU also being available
on 64-bit ARM.

Signed-off-by: Thierry Reding <treding@nvidia•com>
---
 drivers/pci/host/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig
index 75a605426538..d1cdd9c992ac 100644
--- a/drivers/pci/host/Kconfig
+++ b/drivers/pci/host/Kconfig
@@ -14,6 +14,7 @@ config PCI_DRA7XX
 config PCI_MVEBU
 	bool "Marvell EBU PCIe controller"
 	depends on ARCH_MVEBU || ARCH_DOVE
+	depends on ARM
 	depends on OF
 
 config PCIE_DW
-- 
2.7.1

             reply	other threads:[~2016-02-18 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 13:32 Thierry Reding [this message]
2016-02-18 14:06 ` [PATCH] PCI: mvebu: Restrict build to 32-bit ARM Arnd Bergmann
2016-02-18 14:24   ` Thierry Reding
2016-02-18 14:34   ` Gregory CLEMENT
2016-02-18 14:41     ` Arnd Bergmann
2016-02-18 14:29 ` Thomas Petazzoni
2016-02-26 19:31 ` Bjorn Helgaas

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=1455802330-17565-1-git-send-email-thierry.reding@gmail.com \
    --to=thierry.reding@gmail$(echo .)com \
    --cc=andrew@lunn$(echo .)ch \
    --cc=bhelgaas@google$(echo .)com \
    --cc=gregory.clement@free-electrons$(echo .)com \
    --cc=jason@lakedaemon$(echo .)net \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-pci@vger$(echo .)kernel.org \
    --cc=sebastian.hesselbarth@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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