From: Tony Lindgren <tony@atomide.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [RFC] ARM Subarchitecture group maintainership
Date: Wed, 25 May 2011 08:34:59 -0700 [thread overview]
Message-ID: <20110525153459.GE27250@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105251021550.3207@xanadu.home>
* Nicolas Pitre <nico@fluxnic.net> [110525 07:24]:
>
> No. We'll start merging stuff once this merge window is over. In other
> words, you are still on your own for the current one.
OK
> Also, I want stuff merged in this subarch tree way before the next merge
> window opens on a continuous basis, not in a big rush before it opens,
> or worse, while it is already open.
OK that sounds good to me. There's at least one more thing to sort out
though:
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?
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM Subarchitecture group maintainership
Date: Wed, 25 May 2011 08:34:59 -0700 [thread overview]
Message-ID: <20110525153459.GE27250@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105251021550.3207@xanadu.home>
* Nicolas Pitre <nico@fluxnic.net> [110525 07:24]:
>
> No. We'll start merging stuff once this merge window is over. In other
> words, you are still on your own for the current one.
OK
> Also, I want stuff merged in this subarch tree way before the next merge
> window opens on a continuous basis, not in a big rush before it opens,
> or worse, while it is already open.
OK that sounds good to me. There's at least one more thing to sort out
though:
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?
Tony
next prev parent reply other threads:[~2011-05-25 15:35 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 [this message]
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
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=20110525153459.GE27250@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--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.