All of lore.kernel.org
 help / color / mirror / Atom feed
From: H Hartley Sweeten <hartleys@visionengravers.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King <linux@arm.linux.org.uk>,
	Nicolas Pitre <nico@fluxnic.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [RFC] ARM Subarchitecture group maintainership
Date: Wed, 25 May 2011 11:19:59 -0500	[thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D323A714@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <20110525082344.GF22096@pengutronix.de>

On Wed, May 18, 2011 at 10:47:16AM +0200, Arnd Bergmann wrote:
> 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@arndb.de>
> Cc: Nicolas Pitre <nico@fluxnic.net>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> 
> ---
> 
> Maintainers: If you are happy with the layout of the process,
> please ack this patch, otherwise please comment.

As co-maintainer of ep93xx

Acked-by: H Hartley Sweeten <hsweeten@visionengravers.com>

WARNING: multiple messages have this Message-ID (diff)
From: hartleys@visionengravers.com (H Hartley Sweeten)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM Subarchitecture group maintainership
Date: Wed, 25 May 2011 11:19:59 -0500	[thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D323A714@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <20110525082344.GF22096@pengutronix.de>

On Wed, May 18, 2011 at 10:47:16AM +0200, Arnd Bergmann wrote:
> 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@arndb.de>
> Cc: Nicolas Pitre <nico@fluxnic.net>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: linux-kernel at vger.kernel.org
> 
> ---
> 
> Maintainers: If you are happy with the layout of the process,
> please ack this patch, otherwise please comment.

As co-maintainer of ep93xx

Acked-by: H Hartley Sweeten <hsweeten@visionengravers.com>

  reply	other threads:[~2011-05-25 16:20 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  8:47 [RFC] ARM Subarchitecture group maintainership Arnd Bergmann
2011-05-18  8:47 ` Arnd Bergmann
2011-05-18 14:53 ` Catalin Marinas
2011-05-18 14:53   ` Catalin Marinas
2011-05-25  7:59   ` Tony Lindgren
2011-05-25  7:59     ` Tony Lindgren
2011-05-25 14:28     ` Nicolas Pitre
2011-05-25 14:28       ` Nicolas Pitre
2011-05-25 15:34       ` Tony Lindgren
2011-05-25 15:34         ` Tony Lindgren
2011-05-25 16:06         ` Thomas Gleixner
2011-05-25 16:06           ` Thomas Gleixner
2011-05-26  8:28           ` Mark Brown
2011-05-26  8:28             ` Mark Brown
2011-05-26  8:33             ` Thomas Gleixner
2011-05-26  8:33               ` Thomas Gleixner
2011-05-26  9:59               ` Mark Brown
2011-05-26  9:59                 ` Mark Brown
2011-05-26 10:13                 ` Arnd Bergmann
2011-05-26 10:13                   ` Arnd Bergmann
2011-05-18 15:22 ` Shawn Guo
2011-05-18 15:22   ` Shawn Guo
2011-05-18 15:27   ` Anca Emanuel
2011-05-18 15:27     ` Anca Emanuel
2011-05-19 12:13   ` Arnd Bergmann
2011-05-19 12:13     ` Arnd Bergmann
2011-05-18 15:56 ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-18 15:56   ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-18 21:24   ` Thomas Gleixner
2011-05-18 21:24     ` Thomas Gleixner
2011-05-18 21:47   ` Catalin Marinas
2011-05-18 21:47     ` Catalin Marinas
2011-05-18 20:49 ` David Brown
2011-05-18 20:49   ` David Brown
2011-05-19  1:27 ` Barry Song
2011-05-19  1:27   ` Barry Song
2011-05-19  2:42   ` Nicolas Pitre
2011-05-19  2:42     ` Nicolas Pitre
2011-05-19  3:01     ` Barry Song
2011-05-19  3:01       ` Barry Song
2011-05-19 13:31       ` Linus Walleij
2011-05-19 13:31         ` Linus Walleij
2011-05-19 19:28         ` Russell King - ARM Linux
2011-05-19 19:28           ` Russell King - ARM Linux
2011-05-19 19:31           ` Nicolas Pitre
2011-05-19 19:31             ` Nicolas Pitre
2011-05-19 13:50       ` Arnd Bergmann
2011-05-19 13:50         ` Arnd Bergmann
2011-05-19 14:23         ` Barry Song
2011-05-19 14:23           ` Barry Song
2011-05-19 15:08           ` Arnd Bergmann
2011-05-19 15:08             ` Arnd Bergmann
2011-05-24  9:23             ` Barry Song
2011-05-24  9:23               ` Barry Song
2011-05-24 12:26               ` Arnd Bergmann
2011-05-24 12:26                 ` Arnd Bergmann
2011-05-27  5:34         ` viresh kumar
2011-05-27  5:34           ` viresh kumar
2011-05-27  7:24           ` Arnd Bergmann
2011-05-27  7:24             ` Arnd Bergmann
2011-05-19 12:20   ` Arnd Bergmann
2011-05-19 12:20     ` Arnd Bergmann
2011-05-19  3:38 ` viresh kumar
2011-05-19  3:38   ` viresh kumar
2011-05-20 20:48 ` Linus Walleij
2011-05-20 20:48   ` Linus Walleij
2011-05-20 20:59 ` Joe Perches
2011-05-20 20:59   ` Joe Perches
2011-05-21  8:23   ` Arnd Bergmann
2011-05-21  8:23     ` Arnd Bergmann
2011-05-25  8:10 ` Nicolas Ferre
2011-05-25  8:10   ` Nicolas Ferre
2011-05-25  8:23 ` Sascha Hauer
2011-05-25  8:23   ` Sascha Hauer
2011-05-25 16:19   ` H Hartley Sweeten [this message]
2011-05-25 16:19     ` H Hartley Sweeten
2011-05-26 16:14 ` Kevin Hilman
2011-05-26 16:14   ` Kevin Hilman
2011-05-27  0:01   ` Kyungmin Park
2011-05-27  0:01     ` Kyungmin Park
2011-07-26 18:03 ` Stephen Boyd
2011-07-26 18:03   ` Stephen Boyd
2011-07-27  1:47   ` Barry Song
2011-07-27  1:47     ` Barry Song
2011-07-27  2:23     ` Stephen Boyd
2011-07-27  2:23       ` Stephen Boyd
2011-07-27 14:55   ` Arnd Bergmann
2011-07-27 14:55     ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0D753D10438DA54287A00B027084269764D323A714@AUSP01VMBX24.collaborationhost.net \
    --to=hartleys@visionengravers.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.