From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel for v3.3
Date: Tue, 10 Jan 2012 22:37:13 +0000 [thread overview]
Message-ID: <20120110223712.GL7164@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201201102013.54958.arnd@arndb.de>
On Tue, Jan 10, 2012 at 08:13:54PM +0000, Arnd Bergmann wrote:
> On Tuesday 10 January 2012, Mark Brown wrote:
> > That sounds like it'd be helpful overall but it's something that has to
> > be sorted out at the maintainer level. I'm guessing there's not really
> > much that contributors can do here?
> I think you did everything as good as you could, we just need to routinely
> call for everyone to submit stuff in time. A number of maintainers sent stuff
> after Christmas (which I expected to start the merge window) and were mostly
> lucky because Linus gave us an extra 10 days to sort things out.
I guess it would also be useful to have some way to compare what's in
-next with what's in the arm-soc tree and chase people if that diff gets
big. I do also wonder if it's worth letting people push stuff to you
more aggressively - right now you seem to be asking people to batch
things up and I wonder if that's making it a it easier for things to end
up dropping on the floor if a time based routine isn't working well for
people.
> end, samsung also did for the most part but not entirely and you were
> unfortunate to be the contributor of the patches that missed out.
It's not just me, I'm just vocal and perhaps more to the point spend a
reasonable amount of time chasing stuff into various trees so want to
figure out if I need to change what I'm doing with that.
next prev parent reply other threads:[~2012-01-10 22:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 23:33 [GIT PULL] Samsung devel for v3.3 Kukjin Kim
2012-01-06 21:58 ` Olof Johansson
2012-01-07 10:09 ` Kukjin Kim
2012-01-08 20:49 ` Mark Brown
2012-01-09 1:21 ` Olof Johansson
2012-01-09 1:40 ` Kukjin Kim
2012-01-09 2:03 ` Olof Johansson
2012-01-09 15:56 ` Arnd Bergmann
2012-01-09 16:11 ` Mark Brown
2012-01-10 9:06 ` Russell King - ARM Linux
2012-01-10 18:31 ` Mark Brown
2012-01-10 18:44 ` Nicolas Pitre
2012-01-10 18:46 ` Mark Brown
2012-01-10 19:00 ` Nicolas Pitre
2012-01-10 20:13 ` Arnd Bergmann
2012-01-10 22:37 ` Mark Brown [this message]
2012-01-11 0:11 ` Olof Johansson
2012-01-11 6:39 ` Kukjin Kim
2012-01-11 16:19 ` Arnd Bergmann
2012-01-11 16:50 ` Olof Johansson
2012-01-11 17:29 ` Mark Brown
2012-01-11 6:20 ` Kukjin Kim
2012-01-09 8:26 ` Mark Brown
2012-01-17 6:40 ` Olof Johansson
2012-01-17 7:23 ` Kukjin Kim
2012-01-17 7:24 ` Olof Johansson
2012-01-17 10:53 ` Mark Brown
2012-01-09 9:58 ` Russell King - ARM Linux
2012-01-09 23:24 ` Mark Brown
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=20120110223712.GL7164@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).