From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Nicolas Pitre <nico@fluxnic.net>,
linux-arm-msm@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] generic arm for MSM
Date: Fri, 26 Mar 2010 11:24:09 +0000 [thread overview]
Message-ID: <20100326112408.GC27692@sirena.org.uk> (raw)
In-Reply-To: <1269557364.21793.52.camel@c-dwalke-linux.qualcomm.com>
On Thu, Mar 25, 2010 at 03:49:24PM -0700, Daniel Walker wrote:
> I only based this pull request on next , since I can't get Russell tree
> anyplace else. I've had patches in the past which I've had to use next
> cause there are underlying changes that I can only find in next .. So no
> I don't base development trees on next generally.
You can see what's pulled into -next by looking at the file Trees in the
root of the -next tree, and the specific commits in a given -next can be
seen by looking at the file SHA1s in the same directory.
As people have said you should *never* send any pull requests based on
-next, it's a constantly rebasing merge of various development trees of
varying quality and so will never be merged into mainline. If you are
sending stuff based on -next for some reason send it as a patches.
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] generic arm for MSM
Date: Fri, 26 Mar 2010 11:24:09 +0000 [thread overview]
Message-ID: <20100326112408.GC27692@sirena.org.uk> (raw)
In-Reply-To: <1269557364.21793.52.camel@c-dwalke-linux.qualcomm.com>
On Thu, Mar 25, 2010 at 03:49:24PM -0700, Daniel Walker wrote:
> I only based this pull request on next , since I can't get Russell tree
> anyplace else. I've had patches in the past which I've had to use next
> cause there are underlying changes that I can only find in next .. So no
> I don't base development trees on next generally.
You can see what's pulled into -next by looking at the file Trees in the
root of the -next tree, and the specific commits in a given -next can be
seen by looking at the file SHA1s in the same directory.
As people have said you should *never* send any pull requests based on
-next, it's a constantly rebasing merge of various development trees of
varying quality and so will never be merged into mainline. If you are
sending stuff based on -next for some reason send it as a patches.
next prev parent reply other threads:[~2010-03-26 11:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 21:52 [GIT PULL] generic arm for MSM Daniel Walker
2010-03-25 21:52 ` Daniel Walker
2010-03-25 22:29 ` Russell King - ARM Linux
2010-03-25 22:29 ` Russell King - ARM Linux
2010-03-25 22:32 ` Daniel Walker
2010-03-25 22:32 ` Daniel Walker
2010-03-25 22:42 ` Russell King - ARM Linux
2010-03-25 22:42 ` Russell King - ARM Linux
2010-03-25 22:46 ` Nicolas Pitre
2010-03-25 22:46 ` Nicolas Pitre
2010-03-25 22:49 ` Daniel Walker
2010-03-25 22:49 ` Daniel Walker
2010-03-25 22:53 ` Russell King - ARM Linux
2010-03-25 22:53 ` Russell King - ARM Linux
2010-03-25 22:54 ` Daniel Walker
2010-03-25 22:54 ` Daniel Walker
2010-03-25 22:55 ` Russell King - ARM Linux
2010-03-25 22:55 ` Russell King - ARM Linux
2010-03-25 23:21 ` Daniel Walker
2010-03-25 23:21 ` Daniel Walker
2010-03-26 8:14 ` Uwe Kleine-König
2010-03-26 8:14 ` Uwe Kleine-König
2010-03-26 8:23 ` Russell King - ARM Linux
2010-03-26 8:23 ` Russell King - ARM Linux
2010-03-26 9:30 ` Uwe Kleine-König
2010-03-26 9:30 ` Uwe Kleine-König
2010-04-01 23:11 ` Daniel Walker
2010-04-01 23:11 ` Daniel Walker
2010-04-06 21:35 ` Russell King - ARM Linux
2010-04-06 21:35 ` Russell King - ARM Linux
2010-04-06 22:00 ` Daniel Walker
2010-04-06 22:00 ` Daniel Walker
2010-04-06 22:04 ` Russell King - ARM Linux
2010-04-06 22:04 ` Russell King - ARM Linux
2010-04-06 22:08 ` Daniel Walker
2010-04-06 22:08 ` Daniel Walker
2010-04-06 22:34 ` H Hartley Sweeten
2010-04-06 22:34 ` H Hartley Sweeten
2010-04-06 22:44 ` Daniel Walker
2010-04-06 22:44 ` Daniel Walker
2010-03-26 13:33 ` Daniel Walker
2010-03-26 13:33 ` Daniel Walker
2010-03-26 11:24 ` Mark Brown [this message]
2010-03-26 11: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=20100326112408.GC27692@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.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.