[PATCH v2 1/5] ARM: Broadcom: Unconditionally build arch/arm/mach-bcm

[Domenico Andreoli]

On Fri, Jul 26, 2013 at 08:39:08PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jul 26, 2013 at 12:09:03PM -0700, Christian Daudt wrote:
> > On 13-07-26 11:47 AM, Russell King - ARM Linux wrote:
> >> On Fri, Jul 26, 2013 at 10:17:33AM -0700, Christian Daudt wrote:
> >>> Because ARCH_BCM is meant to be used for a number of SoC families. We've
> >>> started upstreaming one (the BCM281XX) but have 2 more internally that
> >>> we're working towards upstreaming. And in the future our plan is to keep
> >>> the Broadcom Mobile SoCs all building under this single ARCH_BCM
> >>> configuration as multiplatform code building a single zImage for them.
> >> 1. We're moving to a single zImage for everything.  Not just Broadcom.
> >> There's no need for Broadcom stuff to be treated any differently.
> >> Participate in the single zImage project and you will get that benefit
> >> without these games.
> > I don't follow what is the game being played.
> 
> I don't really mind what you do, but when you start talking about having
> any ARM build always descend into mach-bcm, then something is very wrong
> with how you're going about it - you don't see anyone else needing that
> in the tree, not even OMAP.

That was a Great Idea(tm) of mine that obviously needed some rebuttal.
No insult was implied for those not having had it in solving the very
same problem.

BTW I asked this very same question [1] and got _zero_ feedback so I
thought it was worth a patch.

> I don't really care if your intention is to decend into mach-bcm and then
> do nothing - that's not the point.  The point is we shouldn't even
> decend into mach-bcm if there's nothing to be built there.

I've got the point but didn't fully understand why would be so wrong to
walk one more subdir even if nothing is going to be built.

thanks,
Domenico

[1] http://permalink.gmane.org/gmane.linux.ports.arm.kernel/253500