From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM Subarchitecture group maintainership
Date: Thu, 26 May 2011 12:13:46 +0200 [thread overview]
Message-ID: <201105261213.46804.arnd@arndb.de> (raw)
In-Reply-To: <20110526095919.GA31268@opensource.wolfsonmicro.com>
On Thursday 26 May 2011, Mark Brown wrote:
>
> On Thu, May 26, 2011 at 10:33:55AM +0200, Thomas Gleixner wrote:
> > On Thu, 26 May 2011, Mark Brown wrote:
>
> > > I think the question is about the existing -next branches people already
> > > have - should they contain code that hasn't yet gone to you guys? We're
> > > doing that for audio at the minute (having subtrees in -next directly)
> > > and it's pretty helpful for miniising hassle for the maintainers of the
> > > core tree.
>
> > We obviously talk about arch/arm/[mach|plat]* stuff, drivers/ sound/
> > etc. should go through the relevant maintainer trees.
>
> Right, but the question is what to do with the subtrees that are in
> -next currently. I'm mentioning sound as an example of a tree with
> subtrees in -next directly.
I think all the subarch maintainers should basically stop having their
stuff included directly in linux-next, but instead have it pulled into
our tree, which has one aggregate -next branch that gets included there.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
Nicolas Pitre <nico@fluxnic.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] ARM Subarchitecture group maintainership
Date: Thu, 26 May 2011 12:13:46 +0200 [thread overview]
Message-ID: <201105261213.46804.arnd@arndb.de> (raw)
In-Reply-To: <20110526095919.GA31268@opensource.wolfsonmicro.com>
On Thursday 26 May 2011, Mark Brown wrote:
>
> On Thu, May 26, 2011 at 10:33:55AM +0200, Thomas Gleixner wrote:
> > On Thu, 26 May 2011, Mark Brown wrote:
>
> > > I think the question is about the existing -next branches people already
> > > have - should they contain code that hasn't yet gone to you guys? We're
> > > doing that for audio at the minute (having subtrees in -next directly)
> > > and it's pretty helpful for miniising hassle for the maintainers of the
> > > core tree.
>
> > We obviously talk about arch/arm/[mach|plat]* stuff, drivers/ sound/
> > etc. should go through the relevant maintainer trees.
>
> Right, but the question is what to do with the subtrees that are in
> -next currently. I'm mentioning sound as an example of a tree with
> subtrees in -next directly.
I think all the subarch maintainers should basically stop having their
stuff included directly in linux-next, but instead have it pulled into
our tree, which has one aggregate -next branch that gets included there.
Arnd
next prev parent reply other threads:[~2011-05-26 10:13 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 [this message]
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
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=201105261213.46804.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.