linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	rmk+kernel@arm.linux.org.uk, linux-pci@vger.kernel.org
Subject: Re: [PATCH 09/13] PCI: Remove ARCH_KIRKWOOD and ARCH_DOVE dependency
Date: Sat, 5 Jul 2014 11:54:58 -0600	[thread overview]
Message-ID: <20140705175458.GF26618@google.com> (raw)
In-Reply-To: <1404075603-31838-12-git-send-email-andrew@lunn.ch>

On Sun, Jun 29, 2014 at 10:59:58PM +0200, Andrew Lunn wrote:
> mach-kirkwood and mach-dove have been removed, now that these SoCs
> lives in mach-mvebu. ARCH_MVEBU is sufficient.

Looks like there's still discussion about the cubox regression, so
I'll wait until that's resolved and Thomas or Jason ack this.

> 
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org
> ---
>  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 21df477be0c8..b9692deeb99a 100644
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> @@ -3,7 +3,7 @@ menu "PCI host controller drivers"
>  
>  config PCI_MVEBU
>  	bool "Marvell EBU PCIe controller"
> -	depends on ARCH_MVEBU || ARCH_DOVE || ARCH_KIRKWOOD
> +	depends on ARCH_MVEBU
>  	depends on OF
>  
>  config PCIE_DW
> -- 
> 2.0.0
> 

  reply	other threads:[~2014-07-05 17:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 20:59 [PATCH 00/13] Remove mach-kirkwood and mach-dove Andrew Lunn
2014-06-29 20:59 ` [PATCH 09/13] PCI: Remove ARCH_KIRKWOOD and ARCH_DOVE dependency Andrew Lunn
2014-07-05 17:54   ` Bjorn Helgaas [this message]
2014-07-05 17:52     ` Andrew Lunn
2014-06-29 21:35 ` [PATCH 00/13] Remove mach-kirkwood and mach-dove Russell King - ARM Linux
2014-06-30  7:16   ` [alsa-devel] " Jean-Francois Moine
2014-06-30  8:49     ` Russell King - ARM Linux
2014-06-30  9:47       ` Jean-Francois Moine
2014-06-30 10:00         ` Russell King - ARM Linux
2014-06-30 12:15   ` Sebastian Hesselbarth
2014-06-30 12:43     ` Russell King - ARM Linux
2014-06-30 13:22       ` Sebastian Hesselbarth
2014-06-30 14:25         ` Russell King - ARM Linux
2014-06-30 15:35           ` Sebastian Hesselbarth
2014-06-30 16:56             ` Russell King - ARM Linux
2014-06-30 17:31               ` Sebastian Hesselbarth
2014-06-30 19:35                 ` Russell King - ARM Linux
2014-06-30 17:43               ` Andrew Lunn
2014-06-30 18:08                 ` Russell King - ARM Linux
2014-06-30 18:16                   ` Andrew Lunn
2014-07-06  9:49                     ` [rtc-linux] " Alexander Holler
2014-06-30 22:21           ` Ezequiel Garcia
2014-07-08 12:13 ` Jason Cooper

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=20140705175458.GF26618@google.com \
    --to=bhelgaas@google.com \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-pci@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=sebastian.hesselbarth@googlemail.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).