linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] ARM: Broadcom: Unconditionally build arch/arm/mach-bcm
Date: Sat, 27 Jul 2013 01:28:58 +0200	[thread overview]
Message-ID: <20130726232858.GA6953@glitch> (raw)
In-Reply-To: <20130726231108.GA10812@obsidianresearch.com>

On Fri, Jul 26, 2013 at 05:11:08PM -0600, Jason Gunthorpe wrote:
> On Fri, Jul 26, 2013 at 11:59:00PM +0200, Domenico Andreoli wrote:
> 
> > In mach-bcm we (or I, it's not very clear to me) want to have support for
> > multiple SoCs.
> > 
> > In trying the approach
> > 
> > machine-$(CONFIG_ARCH_BCM)		+= bcm
> > machine-$(CONFIG_ARCH_BCM4760)		+= bcm
> > 
> > I got linker complains about multiple symbol definitiion in case both the
> > config options are selected.
> 
> You can't repeat the same dir. Maybe this?
> 
> bcm-machine-$(CONFIG_ARCH_BCM) := bmc
> bcm-machine-$(CONFIG_ARCH_BCM4760) := bmc
> machine-y += $(bcm-machine-y)

nice! I prefer this to the config option used only to descend the dir,
you never know how it is going to be abused.

Christian, would you agree in ditching ARCH_BROADCOM then?

Russel, is it ok?

thanks,
Domenico

  reply	other threads:[~2013-07-26 23:28 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
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 [this message]
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=20130726232858.GA6953@glitch \
    --to=cavokz@gmail.com \
    --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).