[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1105261030560.3078@ionos>
Date: Thu, 26 May 2011 10:33:55 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
cc: Tony Lindgren <tony@...mide.com>,
Russell King <linux@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Nicolas Pitre <nico@...xnic.net>,
Marc Zyngier <marc.zyngier@....com>,
Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC] ARM Subarchitecture group maintainership
On Thu, 26 May 2011, Mark Brown wrote:
> On Wed, May 25, 2011 at 06:06:16PM +0200, Thomas Gleixner wrote:
> > On Wed, 25 May 2011, Tony Lindgren wrote:
>
> > > What do you want to do with with the various for-next branches?
>
> > > Do you want to queue things into your tree before hitting for-next?
>
> > The stuff which gets pulled in from the various suppliers is
> > aggregated in a separate for -next branch.
>
> 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.
Thanks,
tglx
--
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