linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mporter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: bcm: Restrict ARCH_BCM selection to ARCH_MULTI_V6_V7
Date: Fri, 25 Apr 2014 09:54:15 -0400	[thread overview]
Message-ID: <20140425135415.GF1127@beef> (raw)
In-Reply-To: <1396340779-20550-1-git-send-email-shc_work@mail.ru>

On Tue, Apr 01, 2014 at 12:26:19PM +0400, Alexander Shiyan wrote:
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>

Applied to mach-bcm for-3.16/soc but I added a proper commit message.
Please always have some description so we know why a patch is needed
even when it seems trivial.

Thanks,
Matt

>  arch/arm/mach-bcm/Kconfig | 11 +++--------
>  1 file changed, 3 insertions(+), 8 deletions(-)
> 
> diff --git a/arch/arm/mach-bcm/Kconfig b/arch/arm/mach-bcm/Kconfig
> index 21f97f7..1048ba1 100644
> --- a/arch/arm/mach-bcm/Kconfig
> +++ b/arch/arm/mach-bcm/Kconfig
> @@ -1,13 +1,10 @@
>  config ARCH_BCM
> -	bool "Broadcom SoC Support"
> -	depends on ARCH_MULTIPLATFORM
> +	bool "Broadcom SoC Support" if ARCH_MULTI_V6_V7
>  	help
> -	  This enables support for Broadcom ARM based SoC
> -          chips
> -
> -if ARCH_BCM
> +	  This enables support for Broadcom ARM based SoC chips
>  
>  menu "Broadcom SoC Selection"
> +	depends on ARCH_BCM
>  
>  config ARCH_BCM_MOBILE
>  	bool "Broadcom Mobile SoC" if ARCH_MULTI_V7
> @@ -71,5 +68,3 @@ config ARCH_BCM_5301X
>  	  network SoC using a MIPS CPU, they are supported by arch/mips/bcm47xx
>  
>  endmenu
> -
> -endif
> -- 
> 1.8.3.2
> 

      parent reply	other threads:[~2014-04-25 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  8:26 [PATCH] ARM: bcm: Restrict ARCH_BCM selection to ARCH_MULTI_V6_V7 Alexander Shiyan
2014-04-01 16:31 ` Tim Kryger
2014-04-01 16:34   ` Tim Kryger
2014-04-25 13:54 ` Matt Porter [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=20140425135415.GF1127@beef \
    --to=mporter@linaro.org \
    --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).