From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/5] MSM changes for 3.7 merge window
Date: Thu, 13 Sep 2012 11:53:42 -0700 [thread overview]
Message-ID: <20120913185342.GA29823@codeaurora.org> (raw)
Following are 5 pull requests for the MSM SoC. The first 5 are
cleanups, fixes, devicetree, and some board changes that finally allow
us to build more than one SoC into a single kernel image.
The fifth patch is my merge, which can be used as a reference to the
intended merge resolution.
David
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2012-09-13 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 18:53 David Brown [this message]
2012-09-13 18:56 ` [GIT PULL 2/5] msm non-critical fixes David Brown
2012-09-13 18:56 ` [GIT PULL 3/5] msm devicetree changes David Brown
2012-09-13 18:57 ` [GIT PULL 4/5] msm board changes David Brown
2012-09-13 18:58 ` [GIT PULL 5/5] msm all changes David Brown
2012-09-13 18:59 ` [GIT PULL 1/5] msm cleanups (resend) David Brown
2012-09-17 1:06 ` [GIT PULL 0/5] MSM changes for 3.7 merge window Olof Johansson
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=20120913185342.GA29823@codeaurora.org \
--to=davidb@codeaurora.org \
--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).