All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] generic arm for MSM
Date: Thu, 25 Mar 2010 15:49:24 -0700	[thread overview]
Message-ID: <1269557364.21793.52.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003251843320.694@xanadu.home>

On Thu, 2010-03-25 at 18:46 -0400, Nicolas Pitre wrote:
> On Thu, 25 Mar 2010, Daniel Walker wrote:
> 
> > These are all mostly small patches that I've sent out a few times with
> > no comments. Let me know if you see any issues.
> > 
> > The following changes since commit 7ee744f22ffad619e23912a22d1b2795e10ed825:
> >   Stephen Rothwell (1):
> >         Add linux-next specific files for 20100324
> 
> Never base your tree on linux-next.  You really should use a stable 
> tree, such as Linus' tree.  The linux-next tree is constantly thrown 
> away and rebuilt, and your own tree will keep a reference on that 
> obsoleted linux-next version otherwise.

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.

Daniel


WARNING: multiple messages have this Message-ID (diff)
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] generic arm for MSM
Date: Thu, 25 Mar 2010 15:49:24 -0700	[thread overview]
Message-ID: <1269557364.21793.52.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003251843320.694@xanadu.home>

On Thu, 2010-03-25 at 18:46 -0400, Nicolas Pitre wrote:
> On Thu, 25 Mar 2010, Daniel Walker wrote:
> 
> > These are all mostly small patches that I've sent out a few times with
> > no comments. Let me know if you see any issues.
> > 
> > The following changes since commit 7ee744f22ffad619e23912a22d1b2795e10ed825:
> >   Stephen Rothwell (1):
> >         Add linux-next specific files for 20100324
> 
> Never base your tree on linux-next.  You really should use a stable 
> tree, such as Linus' tree.  The linux-next tree is constantly thrown 
> away and rebuilt, and your own tree will keep a reference on that 
> obsoleted linux-next version otherwise.

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.

Daniel

  reply	other threads:[~2010-03-25 22:49 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 [this message]
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
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=1269557364.21793.52.camel@c-dwalke-linux.qualcomm.com \
    --to=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.