[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140811195137.GB3711@ld-irv-0074>
Date: Mon, 11 Aug 2014 12:51:37 -0700
From: Brian Norris <computersforpeace@...il.com>
To: Olof Johansson <olof@...om.net>
Cc: torvalds@...ux-foundation.org, arm@...nel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Matt Porter <mporter@...aro.org>,
Russell King <linux@....linux.org.uk>, robherring2@...il.com,
Florian Fainelli <f.fainelli@...il.com>,
Marc Carino <marc.ceeeee@...il.com>,
Gregory Fong <gregory.0xf0@...il.com>
Subject: Re: [GIT PULL 2/7] ARM: SoC platform changes for 3.17
+ other involved parties
On Fri, Aug 08, 2014 at 09:47:54AM -0700, Olof Johansson wrote:
> This is the bulk of new SoC enablement and other platform changes for 3.17:
[...]
> * Broadcom BCM7xxx settop box chipset is introduced
[...]
> Marc Carino (1):
> ARM: brcmstb: add infrastructure for ARM-based Broadcom STB SoCs
I realize this is a bit late (the pull request is already merged), but
I'd like to be up-front about this: there were some (late) oustanding
review comments made on this patch [1]. I have a few patches queued
locally for addressing many of them, but not all of the issues are
completely resolved.
Shall I simply send a revert patch for the
arch/arm/mach-bcm/platsmp-brcmstb.c stuff, and get it in through the
bcm -> arm-soc -> Linus merge path in 3.17-rcX? Or should I take the
incremental improvement approach, as we have functioning code with no
clear alternative proposal yet?
Again, sorry for the late noise.
Brian
[1] version 8 patch:
http://article.gmane.org/gmane.linux.ports.arm.kernel/343391
--
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