From: Arnd Bergmann <arnd@arndb.de>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Nicolas Pitre <nico@fluxnic.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
"FTPAdmin Kernel.org" <ftpadmin@kernel.org>
Subject: Re: [RFC] ARM Subarchitecture group maintainership
Date: Thu, 19 May 2011 14:13:10 +0200 [thread overview]
Message-ID: <201105191413.10480.arnd@arndb.de> (raw)
In-Reply-To: <20110518152237.GA26055@S2100-06.ap.freescale.net>
On Wednesday 18 May 2011, Shawn Guo wrote:
> On Wed, May 18, 2011 at 10:47:16AM +0200, Arnd Bergmann wrote:
> [...]
> > +ARM SUBARCHITECTURES
> > +M: Arnd Bergmann <arnd@arndb.de>
> > +M: Nicolas Pitre <nico@fluxnic.net>
> > +M: Thomas Gleixner <tglx@linutronix.de>
> > +M: arm@kernel.org
> > +L: linux-arm-kernel@lists.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
>
> Is this repository ready for use yet? It seems not for me.
No, not yet. Once we are sure about the initial set of people in the group,
we can set up the arm@kernel.org alias and the group that lets us write
into the /pub/scm/linux/kernel/git/arm directory.
Also, I wouldn't mind changing the name, if someone comes up with a better
term than arm-subarch.git.
Arnd
next prev parent reply other threads:[~2011-05-19 12:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 8:47 [RFC] ARM Subarchitecture group maintainership Arnd Bergmann
2011-05-18 14:53 ` Catalin Marinas
2011-05-25 7:59 ` Tony Lindgren
2011-05-25 14:28 ` Nicolas Pitre
2011-05-25 15:34 ` Tony Lindgren
2011-05-25 16:06 ` Thomas Gleixner
2011-05-26 8:28 ` Mark Brown
2011-05-26 8:33 ` Thomas Gleixner
2011-05-26 9:59 ` Mark Brown
2011-05-26 10:13 ` Arnd Bergmann
2011-05-18 15:22 ` Shawn Guo
2011-05-18 15:27 ` Anca Emanuel
2011-05-19 12:13 ` Arnd Bergmann [this message]
2011-05-18 15:56 ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-18 21:24 ` Thomas Gleixner
2011-05-18 21:47 ` Catalin Marinas
2011-05-18 20:49 ` David Brown
2011-05-19 1:27 ` Barry Song
2011-05-19 2:42 ` Nicolas Pitre
2011-05-19 3:01 ` Barry Song
2011-05-19 13:31 ` Linus Walleij
2011-05-19 19:28 ` Russell King - ARM Linux
2011-05-19 19:31 ` Nicolas Pitre
2011-05-19 13:50 ` Arnd Bergmann
2011-05-19 14:23 ` Barry Song
2011-05-19 15:08 ` Arnd Bergmann
2011-05-24 9:23 ` Barry Song
2011-05-24 12:26 ` Arnd Bergmann
2011-05-27 5:34 ` viresh kumar
2011-05-27 7:24 ` Arnd Bergmann
2011-05-19 12:20 ` Arnd Bergmann
2011-05-19 3:38 ` viresh kumar
2011-05-20 20:48 ` Linus Walleij
2011-05-20 20:59 ` Joe Perches
2011-05-21 8:23 ` Arnd Bergmann
2011-05-25 8:10 ` Nicolas Ferre
2011-05-25 8:23 ` Sascha Hauer
2011-05-25 16:19 ` H Hartley Sweeten
2011-05-26 16:14 ` Kevin Hilman
2011-05-27 0:01 ` Kyungmin Park
2011-07-26 18:03 ` Stephen Boyd
2011-07-27 1:47 ` Barry Song
2011-07-27 2:23 ` Stephen Boyd
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=201105191413.10480.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ftpadmin@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=shawn.guo@freescale.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox