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-next>] [day] [month] [year] [list]
Date:	Fri, 19 Sep 2014 11:17:11 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	arnd@...db.de, olof@...om.net, arm@...nel.org, mporter@...aro.org,
	bcm@...thebug.org, jonathar@...adcom.com, sbranden@...adcom.com,
	rjui@...adcom.com, linux-kernel@...r.kernel.org,
	bcm-kernel-feedback-list@...adcom.com, hauke@...ke-m.de,
	swarren@...dotorg.org, computersforpeace@...il.com,
	marc.ceeeee@...il.com, cernekee@...il.com, gregory.0xf0@...il.com,
	Florian Fainelli <f.fainelli@...il.com>
Subject: [PATCH] ARM: mach-bcm: offer a new maintainer and process

Hi all,

As some of you may have seen in the news, Broadcom has recently stopped
its mobile SoC activities. Upstream support for Broadcom's Mobile SoCs
was an effort initially started by Christian Daudt and his team, and then
continued by Alex Eleder and Matter Porter assigned to a particular landing
team within Linaro to help Broadcom doing so.

As part of this effort, Christian and Matt volunteered for centralizing pull
requests coming from the arch/arm/mach-bcm/* directory and as of today, they
are still responsible for merging mach-bcm pull requests coming from brcmstb,
bcm5301x, bcm2835 and bcm63xx, creating an intermediate layer to the arm-soc
tree.

Following the mobile group shut down, our group (in which Brian, Gregory, Marc,
Kevin and myself are) inherited these mobile SoC platforms, although at this
point we cannot comment on the future of mobile platforms, we know that our
Linaro activities have been stopped.

We have not heard much from Christian and Matt in a while, and some of our pull
requests have been stalling as a result. We would like to offer both a new
maintainer for the mobile platforms as well as reworking the pull request
process:

- our group has now full access to these platforms, putting us in the best
  position to support Mobile SoCs questions

- over time, we think that the brcmstb, bcm5301x, bcm63xx and now Cygnus code
  bases will represent the major bulk of the mach-bcm code changes submitted,
  mobile SoCs being in deep maintenance mode

- we want to keep our submission pace high, and keep a smooth and responsive
  process in place for other maintainers such as Hauke Merthens and Stephen
  Warren and now Scott Branden and his team for Cygnus/Northstar+.

- there is little to no code sharing within mach-bcm, so we think each group
  of maintainers should send individual pull requests towards Arnd and Olof,
  the only conflicts they should ever have to resolve are for the Makefile and
  Kconfig files, not different than any other pull requests

Ideally, we would like Christian and Matt to acknowledge that change, if we
cannot get an answer within the next 3 weeks, we think this change
should go in to unblock the current situation.

Florian Fainelli (1):
  MAINTAINERS: add a third maintainer to mach-bcm

 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1

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