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 18:46:43 +0000 [thread overview]
Message-ID: <20120110184643.GF7164@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1201101341040.2722@xanadu.home>
On Tue, Jan 10, 2012 at 01:44:54PM -0500, Nicolas Pitre wrote:
> On Tue, 10 Jan 2012, Mark Brown wrote:
> > So, is there anything that people like me who are contributing to rather
> > than maintaining things can do to help here beyond chasing maintainers?
> Maybe the Samsung maintainer(s) should target early merge into the
> arm-soc tree instead of going straight to linux-next only. The former
> ends up in the later anyway.
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?
next prev parent reply other threads:[~2012-01-10 18:46 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 [this message]
2012-01-10 19:00 ` Nicolas Pitre
2012-01-10 20:13 ` Arnd Bergmann
2012-01-10 22:37 ` Mark Brown
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=20120110184643.GF7164@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).