From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/4] mxs changes for 3.7
Date: Tue, 11 Sep 2012 15:54:55 +0800 [thread overview]
Message-ID: <1347350100-4674-1-git-send-email-shawn.guo@linaro.org> (raw)
Hi Arnd, Olof,
Here are the pull requests of mxs changes for 3.7. This is the first
time I use signed tags, and the dependencies are mentioned in tag
messages. Please have a look and take care of them. Thanks.
Regards,
Shawn
next reply other threads:[~2012-09-11 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 7:54 Shawn Guo [this message]
2012-09-11 7:54 ` [GIT PULL 1/4] mxs device tree changes for 3.7 Shawn Guo
2012-09-13 5:48 ` Olof Johansson
2012-09-11 7:54 ` [GIT PULL 2/4] mxs sparse-irq support Shawn Guo
2012-09-13 5:56 ` Olof Johansson
2012-09-13 6:16 ` Shawn Guo
2012-09-13 7:42 ` Olof Johansson
2012-09-11 7:54 ` [GIT PULL 3/4] mxs clk device tree lookup Shawn Guo
2012-09-11 8:58 ` Shawn Guo
2012-09-13 6:08 ` Olof Johansson
2012-09-13 17:23 ` Turquette, Mike
2012-09-11 7:54 ` [GIT PULL 4/4] mxs defconfig update for 3.7 Shawn Guo
2012-09-13 6:10 ` Olof Johansson
2012-09-13 6:17 ` Shawn Guo
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=1347350100-4674-1-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.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).