From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mach-bcm: clean up config and build targets
Date: Thu, 03 Apr 2014 22:49:19 +0200 [thread overview]
Message-ID: <1396558159.21212.4.camel@x220> (raw)
In-Reply-To: <1396557052-24029-1-git-send-email-elder@linaro.org>
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@linaro.org>
> ---
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Alex Elder <elder@linaro.org>
Cc: bcm@fixthebug.org, mporter@linaro.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mach-bcm: clean up config and build targets
Date: Thu, 03 Apr 2014 22:49:19 +0200 [thread overview]
Message-ID: <1396558159.21212.4.camel@x220> (raw)
In-Reply-To: <1396557052-24029-1-git-send-email-elder@linaro.org>
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@linaro.org>
> ---
Paul Bolle
next prev parent reply other threads:[~2014-04-03 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 20:30 [PATCH] mach-bcm: clean up config and build targets Alex Elder
2014-04-03 20:30 ` Alex Elder
2014-04-03 20:49 ` Paul Bolle [this message]
2014-04-03 20:49 ` Paul Bolle
2014-04-03 21:02 ` Alex Elder
2014-04-03 21:02 ` Alex Elder
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=1396558159.21212.4.camel@x220 \
--to=pebolle@tiscali.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.