linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	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 22:53:00 +0000	[thread overview]
Message-ID: <20100325225300.GK24984@n2100.arm.linux.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:
> 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.

http://www.home.arm.linux.org.uk/developer/

has a link to gitweb for it, and a url pointing to where it is on the
ftp/http site:

# rmk's GIT tree
# rmk's random kernel patches and git tree 

It's not like it's hidden.

  reply	other threads:[~2010-03-25 22:53 UTC|newest]

Thread overview: 22+ 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 22:29 ` Russell King - ARM Linux
2010-03-25 22:32   ` Daniel Walker
2010-03-25 22:42     ` Russell King - ARM Linux
2010-03-25 22:46 ` Nicolas Pitre
2010-03-25 22:49   ` Daniel Walker
2010-03-25 22:53     ` Russell King - ARM Linux [this message]
2010-03-25 22:54       ` Daniel Walker
2010-03-25 22:55         ` Russell King - ARM Linux
2010-03-25 23:21           ` Daniel Walker
2010-03-26  8:14             ` Uwe Kleine-König
2010-03-26  8:23               ` Russell King - ARM Linux
2010-03-26  9:30                 ` Uwe Kleine-König
2010-04-01 23:11                 ` Daniel Walker
2010-04-06 21:35                   ` Russell King - ARM Linux
2010-04-06 22:00                     ` Daniel Walker
2010-04-06 22:04                       ` Russell King - ARM Linux
2010-04-06 22:08                         ` Daniel Walker
2010-04-06 22:34                           ` H Hartley Sweeten
2010-04-06 22:44                             ` Daniel Walker
2010-03-26 13:33               ` Daniel Walker
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=20100325225300.GK24984@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --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 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).