From: dwalker@fifo99.com (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [Git pull] MSM for v2.6.39
Date: Wed, 23 Mar 2011 07:23:11 -0700 [thread overview]
Message-ID: <1300890191.6117.43.camel@m0nster> (raw)
In-Reply-To: <8yazkotpwk6.fsf@huya.qualcomm.com>
On Thu, 2011-03-17 at 08:59 -0700, David Brown wrote:
> David Brown (16):
> msm: Add CPU queries
> msm: Generalize timer register mappings
> msm: Generalize QGIC registers
> msm: Add MSM 8960 cpu_is check
> Merge branch 'msm-uart' into for-next
> Merge branch 'msm-8960' into for-next
> Merge branch 'msm-sdcc' into for-next
> Merge branch 'msm-fb' into for-next
> Merge branch 'msm-8960' into msm-core
> msm: Remove broken register definition from trout
> msm: Warning fix in trout gpio board file
> Merge branch 'msm-core' into for-next
> Merge branch 'msm-core' into for-next
> Merge branch 'msm-core' into for-next
> msm: Use explicit GPLv2 licenses
> Merge remote branch 'rmk/for-linus' into for-linus
Could you change the "for-next" name to something more interesting like
msm-for-linus .. I think it would be acceptable to just create
msm-for-linus during the merge window and merge all the sub-tree's into
that.
Daniel
next prev parent reply other threads:[~2011-03-23 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 15:59 [Git pull] MSM for v2.6.39 David Brown
2011-03-23 14:23 ` Daniel Walker [this message]
2011-03-23 18:10 ` David 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=1300890191.6117.43.camel@m0nster \
--to=dwalker@fifo99.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).