From: csd@broadcom•com (Christian Daudt)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/5] ARM: Broadcom: Unconditionally build arch/arm/mach-bcm
Date: Fri, 26 Jul 2013 08:55:42 -0700 [thread overview]
Message-ID: <51F29BFE.8000202@broadcom.com> (raw)
In-Reply-To: <20130726152918.GL29916@titan.lakedaemon.net>
[resend in plain text]
On 13-07-26 08:29 AM, Jason Cooper wrote:
> On Fri, Jul 26, 2013 at 04:56:40PM +0200, Domenico Andreoli wrote:
>> From: Domenico Andreoli<domenico.andreoli@linux•com>
>>
>> arch/arm/mach-bcm contains a plurality of Broadcom SoCs, each configured
>> separately. As a matter of flexibility and maintenance, it needs to be
>> always included in the build.
> So if I'm building mach-kirkwood, I _have_ to build Broadcom? What is
> the *specific* problem you're encountering that this solves?
No it won't, as the Makefile inside mach-bcm will only pull in files
based on ARCH_ settings. This move is so that a number different
Broadcom SoCs can co-exist inside the mach-bcm directory.
>> Cc: Christian Daudt<csd@broadcom•com>
>> Cc:linux-arm-kernel at lists.infradead.org
>> Signed-off-by: Domenico Andreoli<domenico.andreoli@linux•com>
>> ---
>> arch/arm/Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Index: b/arch/arm/Makefile
>> ===================================================================
>> --- a/arch/arm/Makefile
>> +++ b/arch/arm/Makefile
>> @@ -145,7 +145,7 @@ textofs-$(CONFIG_ARCH_MSM8960) := 0x0020
>> # Machine directory name. This list is sorted alphanumerically
>> # by CONFIG_* macro name.
>> machine-$(CONFIG_ARCH_AT91) += at91
>> -machine-$(CONFIG_ARCH_BCM) += bcm
>> +machine-y += bcm
>> machine-$(CONFIG_ARCH_BCM2835) += bcm2835
>> machine-$(CONFIG_ARCH_CLPS711X) += clps711x
>> machine-$(CONFIG_ARCH_CNS3XXX) += cns3xxx
>>
>>
This patch is already contained in Hauke's patchset from yesterday (
http://article.gmane.org/gmane.linux.ports.arm.kernel/254986) so you'll
need to sync with him on it. In case yours goes in first:
Acked-by: Christian Daudt <csd@broadcom•com>
Thanks,
csd
next prev parent reply other threads:[~2013-07-26 15:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 14:56 [PATCH v2 0/5] ARM: Broadcom BCM4760 support Domenico Andreoli
2013-07-26 14:56 ` [PATCH v2 1/5] ARM: Broadcom: Unconditionally build arch/arm/mach-bcm Domenico Andreoli
2013-07-26 15:29 ` Jason Cooper
2013-07-26 15:55 ` Christian Daudt [this message]
2013-07-26 17:11 ` Jason Cooper
2013-07-26 17:17 ` Christian Daudt
2013-07-26 17:33 ` Jason Cooper
2013-07-26 18:47 ` Russell King - ARM Linux
2013-07-26 19:09 ` Christian Daudt
2013-07-26 19:39 ` Russell King - ARM Linux
2013-07-26 20:23 ` Christian Daudt
2013-07-26 22:28 ` Domenico Andreoli
2013-07-26 22:38 ` Russell King - ARM Linux
2013-07-26 23:30 ` Domenico Andreoli
2013-07-26 21:59 ` Domenico Andreoli
2013-07-26 23:11 ` Jason Gunthorpe
2013-07-26 23:28 ` Domenico Andreoli
2013-07-26 23:55 ` Christian Daudt
2013-07-26 23:42 ` Russell King - ARM Linux
2013-07-27 0:01 ` Olof Johansson
2013-07-27 0:04 ` Russell King - ARM Linux
2013-07-27 0:05 ` Olof Johansson
2013-07-27 14:38 ` Arnd Bergmann
2013-08-01 14:18 ` Domenico Andreoli
2013-08-01 9:23 ` Florian Fainelli
2013-08-01 14:15 ` Domenico Andreoli
2013-07-26 17:24 ` Olof Johansson
2013-07-26 14:56 ` [PATCH v2 2/5] ARM: bcm4760: Add platform infrastructure Domenico Andreoli
2013-07-26 14:56 ` [PATCH v2 3/5] ARM: bcm4760: Add system timer Domenico Andreoli
2013-07-26 14:56 ` [PATCH v2 4/5] ARM: bcm4760: Add ripple counter Domenico Andreoli
2013-07-26 14:56 ` [PATCH v2 5/5] ARM: bcm4760: Add restart hook Domenico Andreoli
2013-07-26 15:33 ` [PATCH v2 0/5] ARM: Broadcom BCM4760 support 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=51F29BFE.8000202@broadcom.com \
--to=csd@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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