linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM Subarchitecture group maintainership
Date: Wed, 25 May 2011 10:59:02 +0300	[thread overview]
Message-ID: <20110525075902.GH30799@atomide.com> (raw)
In-Reply-To: <BANLkTi=xzrLhHTBynWf4huA9EusfaDwPbA@mail.gmail.com>

* Catalin Marinas <catalin.marinas@arm.com> [110518 17:49]:
> Arnd,
> 
> On 18 May 2011 09:47, Arnd Bergmann <arnd@arndb.de> 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.
> 
> For clarification - the aim of this subarchitecture group is not only
> to coordinate the upstream merging but also take an active (primary)
> role in consolidating the existing code across various
> subarchitectures under arch/arm/.

It's good to see organized effort on consolidating the code.
And Linaro is probably the best place to organize this effort.

Naturally I assume that you guys won't be merging any platform
specific patches without proper acks from the platform maintainers:

Acked-by: Tony Lindgren <tony@atomide.com>

Arnd, do you want to do a practise run with pulling in the omap
code and merging to Linus for this merge window?

Regards,

Tony

  reply	other threads:[~2011-05-25  7:59 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 [this message]
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
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=20110525075902.GH30799@atomide.com \
    --to=tony@atomide.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).