From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@fluxnic.net>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Samsung devel for v3.3
Date: Wed, 11 Jan 2012 17:29:20 +0000 [thread overview]
Message-ID: <20120111172918.GA24213@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOesGMhDeN9N5A+xVGzM2aoO7YWMkxdpYxZ4o1VV42g_NP6tnQ@mail.gmail.com>
On Wed, Jan 11, 2012 at 08:50:54AM -0800, Olof Johansson wrote:
> On Wed, Jan 11, 2012 at 8:19 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > I would also prefer if people stopped having their own trees included
> > in next, but I know that I'm sometimes slow to pick up patches that
> I also have to admit, as tegra maintainer, that it is convenient to
> have my tree in linux-next, and have things show up in linux-next as
> soon as I pick it up, and then send arm-soc pull requests about once a
> week or so. While we should reduce latency to pull into arm-soc,
> getting pull requests daily will be a bit on the heavy side.
Plus it also means that if there are problems you can resolve it
directly rather than having to get the fixes included in a separate tree
which helps cut down on latencies.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel for v3.3
Date: Wed, 11 Jan 2012 17:29:20 +0000 [thread overview]
Message-ID: <20120111172918.GA24213@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOesGMhDeN9N5A+xVGzM2aoO7YWMkxdpYxZ4o1VV42g_NP6tnQ@mail.gmail.com>
On Wed, Jan 11, 2012 at 08:50:54AM -0800, Olof Johansson wrote:
> On Wed, Jan 11, 2012 at 8:19 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > I would also prefer if people stopped having their own trees included
> > in next, but I know that I'm sometimes slow to pick up patches that
> I also have to admit, as tegra maintainer, that it is convenient to
> have my tree in linux-next, and have things show up in linux-next as
> soon as I pick it up, and then send arm-soc pull requests about once a
> week or so. While we should reduce latency to pull into arm-soc,
> getting pull requests daily will be a bit on the heavy side.
Plus it also means that if there are problems you can resolve it
directly rather than having to get the fixes included in a separate tree
which helps cut down on latencies.
next prev parent reply other threads:[~2012-01-11 17:29 UTC|newest]
Thread overview: 58+ 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-03 23:33 ` Kukjin Kim
2012-01-06 21:58 ` Olof Johansson
2012-01-06 21:58 ` Olof Johansson
2012-01-07 10:09 ` Kukjin Kim
2012-01-07 10:09 ` Kukjin Kim
2012-01-08 20:49 ` Mark Brown
2012-01-08 20:49 ` Mark Brown
2012-01-09 1:21 ` Olof Johansson
2012-01-09 1:21 ` Olof Johansson
2012-01-09 1:40 ` Kukjin Kim
2012-01-09 1:40 ` Kukjin Kim
2012-01-09 2:03 ` Olof Johansson
2012-01-09 2:03 ` Olof Johansson
2012-01-09 15:56 ` Arnd Bergmann
2012-01-09 15:56 ` Arnd Bergmann
2012-01-09 16:11 ` Mark Brown
2012-01-09 16:11 ` Mark Brown
2012-01-10 9:06 ` Russell King - ARM Linux
2012-01-10 9:06 ` Russell King - ARM Linux
2012-01-10 18:31 ` Mark Brown
2012-01-10 18:31 ` Mark Brown
2012-01-10 18:44 ` Nicolas Pitre
2012-01-10 18:44 ` Nicolas Pitre
2012-01-10 18:46 ` Mark Brown
2012-01-10 18:46 ` Mark Brown
2012-01-10 19:00 ` Nicolas Pitre
2012-01-10 19:00 ` Nicolas Pitre
2012-01-10 20:13 ` Arnd Bergmann
2012-01-10 20:13 ` Arnd Bergmann
2012-01-10 22:37 ` Mark Brown
2012-01-10 22:37 ` Mark Brown
2012-01-11 0:11 ` Olof Johansson
2012-01-11 0:11 ` Olof Johansson
2012-01-11 6:39 ` Kukjin Kim
2012-01-11 6:39 ` Kukjin Kim
2012-01-11 16:19 ` Arnd Bergmann
2012-01-11 16:19 ` Arnd Bergmann
2012-01-11 16:50 ` Olof Johansson
2012-01-11 16:50 ` Olof Johansson
2012-01-11 17:29 ` Mark Brown [this message]
2012-01-11 17:29 ` Mark Brown
2012-01-11 6:20 ` Kukjin Kim
2012-01-11 6:20 ` Kukjin Kim
2012-01-09 8:26 ` Mark Brown
2012-01-09 8:26 ` Mark Brown
2012-01-17 6:40 ` Olof Johansson
2012-01-17 6:40 ` Olof Johansson
2012-01-17 7:23 ` Kukjin Kim
2012-01-17 7:23 ` Kukjin Kim
2012-01-17 7:24 ` Olof Johansson
2012-01-17 7:24 ` Olof Johansson
2012-01-17 10:53 ` Mark Brown
2012-01-17 10:53 ` Mark Brown
2012-01-09 9:58 ` Russell King - ARM Linux
2012-01-09 9:58 ` Russell King - ARM Linux
2012-01-09 23:24 ` Mark Brown
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=20120111172918.GA24213@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=olof@lixom.net \
/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.