[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1396558159.21212.4.camel@x220>
Date: Thu, 03 Apr 2014 22:49:19 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Alex Elder <elder@...aro.org>
Cc: bcm@...thebug.org, mporter@...aro.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mach-bcm: clean up config and build targets
On Thu, 2014-04-03 at 15:30 -0500, Alex Elder wrote:
> Currently CONFIG_ARCH_BCM_MOBILE is used to select all Broadcom
> mobile SoCs. Instead, use that only as a config menu switch, and
> define specific symbols like CONFIG_ARCH_BCM_281XX to select a
> particular SoC family. If ARCH_BCM_MOBILE is selected, all of the
> SoCs will be selected by default, but this way each can be disabled
> individually as well.
>
> This allows more precision in controlling what gets built under
> mach-bcm. Another benefit to doing this is that it makes it obvious
> that the code that implements SMC calls to control L2 cache is only
> used for BCM281XX (for example).
>
> Also use Kbuild's $(<modulename>-y) variable mechanism to build a
> single object file containing everything used for the bcm281xx board
> in arch/arm/mach-bcm.
>
> Note: This patch is based on the current arm-soc/for-next branch:
> e98cd72 arm-soc: document samsung merges
>
> The patch is available here:
> http://git.linaro.org/landing-teams/working/broadcom/kernel.git
> Branch review/mach-bcm-cleanup
It seems the last two paragraphs should actually be below the "---"
marker. There's no need to include them in the commit explanation, is
there?
> Signed-off-by: Alex Elder <elder@...aro.org>
> ---
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists