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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Aug 2014 12:51:37 -0700
From:	Brian Norris <>
To:	Olof Johansson <>
	Matt Porter <>,
	Russell King <>,,
	Florian Fainelli <>,
	Marc Carino <>,
	Gregory Fong <>
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.


[1] version 8 patch:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists