lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 11 Aug 2014 13:35:03 -0700
From:	Olof Johansson <olof@...om.net>
To:	Brian Norris <computersforpeace@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"arm@...nel.org" <arm@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Matt Porter <mporter@...aro.org>,
	Russell King <linux@....linux.org.uk>,
	Rob Herring <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

On Mon, Aug 11, 2014 at 12:51 PM, Brian Norris
<computersforpeace@...il.com> wrote:
> + 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?

Yeah, looks like the discussion happened the first day I was on
vacation and I missed the thread in the backlog. :(

Looks like all the outstanding issues are with the SMP support. How
about you send a patch that removes/stubs those portions? It won't be
a pure revert since as mentioned in the thread SMP was combined with
platform support, but that's OK.

That way the basic platform stuff can still go in for 3.17, and we can
re-queue the SMP pieces for 3.18 once things are sorted out.


-Olof
--
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