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  linux-cve-announce  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]
Message-Id: <201105181047.17309.arnd@arndb.de>
Date:	Wed, 18 May 2011 10:47:16 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	linux-kernel@...r.kernel.org,
	Russell King <linux@....linux.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Nicolas Pitre <nico@...xnic.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: [RFC] ARM Subarchitecture group maintainership

This is the draft plan for maintaining the ARM subarchitectures in a common
tree, as a way to help coordinate the upstream merging of the
arch/arm/{plat,mach}-* changes into Linus' tree.

This was discussed in great length at the Linaro Developer Summit in Budapest
last week where we worked out an initial plan. We are modeling the maintainance
after how the linux-tip tree is used for the x86 architecture, with a set
of developers that have commit access to one tree on kernel.org and
have mutual trust in one another. Nicolas Pitre and me are funded
by Linaro to do the bulk of the work, while Thomas Gleixner will help
us part-time with his long time architecture maintainance experience.
Despite the funding by Linaro, this is not a Linaro project and all
ARM subarchitectures are welcome to go through our tree.

Russell King's role as ARM maintainer is of course unchanged by this, but
he has the same commit access to the new tree as the other maintainers and
is welcome to work in the same tree. We are also open to nominations for
further people outside of Linaro to join us as committers. Marc Zyngier from
ARM ltd is one of the candidates that has been suggested and I would also
like to see someone from Google. We have to find the right balance with the
number of committers so we get all the work done without stepping on each
other's toes.

Our tree will be strictly organized in topic brances so we can feed them
upstream in the bitesized chunks that Linus likes. The master branch
is an integration branch that pulls all other branches that are scheduled
for the next merge window and itself gets integrated into linux-next.

We will probably not be fully functional during the 2.6.40 merge window,
but we are trying our best to be useful. For 2.6.41, my hope is that
we can merge the bulk of the ARM subarchitecture changes through this
tree. Once Linus is happy with the way that the process works, we can
mandate that all ARM subarchitecture changes go through our tree, until
then it stays voluntary.

Signed-off-by: Arnd Bergmann <arnd@...db.de>
Cc: Nicolas Pitre <nico@...xnic.net>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Russell King <linux@....linux.org.uk>
Cc: linux-arm-kernel@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org

---

Maintainers: If you are happy with the layout of the process,
please ack this patch, otherwise please comment.

diff --git a/MAINTAINERS b/MAINTAINERS
index 8fce5e6..942d052 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -630,6 +630,17 @@ S:	Maintained
 F:	drivers/amba/
 F:	include/linux/amba/bus.h
 
+ARM SUBARCHITECTURES
+M:	Arnd Bergmann <arnd@...db.de>
+M:	Nicolas Pitre <nico@...xnic.net>
+M:	Thomas Gleixner <tglx@...utronix.de>
+M:	arm@...nel.org
+L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
+S:	MAINTAINED
+F:	arch/arm/mach-*/
+F:	arch/arm/plat-*/
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-subarch.git
+
 ARM/ADI ROADRUNNER MACHINE SUPPORT
 M:	Lennert Buytenhek <kernel@...tstofly.org>
 L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ