linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: mvebu: make Marvell PCIe driver depend on OF
Date: Fri, 9 Aug 2013 08:38:26 -0300	[thread overview]
Message-ID: <20130809113825.GD2848@localhost> (raw)
In-Reply-To: <1376044550-30572-1-git-send-email-thomas.petazzoni@free-electrons.com>

On Fri, Aug 09, 2013 at 12:35:50PM +0200, Thomas Petazzoni wrote:
> The Marvell PCIe host controller driver is heavily tied to Device Tree
> APIs, and can only be used on platforms where the Device Tree is
> used. Therefore, it should "depends on OF" to avoid build failures on
> !OF configurations.
> 
> Reported-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>

> ---
> Bjorn, you can take this one through your tree. Either for 3.11 or
> 3.12, at your preference.
> ---
>  drivers/pci/host/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig
> index 1184ff6..e5ba4eb 100644
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> @@ -4,6 +4,7 @@ menu "PCI host controller drivers"
>  config PCI_MVEBU
>  	bool "Marvell EBU PCIe controller"
>  	depends on ARCH_MVEBU || ARCH_KIRKWOOD
> +	depends on OF
>  
>  config PCIE_DW
>  	bool
> -- 
> 1.8.1.2
> 

-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2013-08-09 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 10:35 [PATCH] PCI: mvebu: make Marvell PCIe driver depend on OF Thomas Petazzoni
2013-08-09 11:38 ` Ezequiel Garcia [this message]
2013-08-09 17:08 ` 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=20130809113825.GD2848@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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).