From: jason77.wang@gmail.com (Jason Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4]Refine iomux files for i.MX51
Date: Sat, 12 Jun 2010 22:22:35 +0800 [thread overview]
Message-ID: <1276352559-8105-1-git-send-email-jason77.wang@gmail.com> (raw)
Through the discussion, I divide my patches to 3 parts.
part1: mx51 iomux related part, the first patch in this part is from
Amit, other patches are based off this patch and they are some
fix or adding definitions for imx51_3ds board.
part2: mxc common cpld debugboard patches. In this part, include a
reverting mx31_3ds patch. I have made built and bootup test
for mx31_3ds platform.
part3: adding mx51_3ds platform patches.
Because part3 depends on part1 and part2, while part1 and part2 are
independent mutually, i will send part1 and part2 first, if these
two parts are passed review, then i will send part3.
part1:
[PATCH 1/4] mxc: Fix pad names for imx51
[PATCH 2/4] mx51/iomux: Fix mux mode and input path for two pads
[PATCH 3/4] mx51/iomux: add UART and GPIO pad definitions for imx51_3ds board
[PATCH 4/4] mxc/iomux: add GPIO bank offset for iomux v3 platforms
part2:
[PATCH 1/2] mxc: add common debug board for 3-stack platforms
[PATCH 2/2] mx31_3ds: revert cpld debug board relate code
next reply other threads:[~2010-06-12 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 14:22 Jason Wang [this message]
2010-06-12 14:22 ` [PATCH 1/4] mxc: Fix pad names for imx51 Jason Wang
2010-06-12 14:22 ` [PATCH 2/4] mx51/iomux: Fix mux mode and input path for two pads Jason Wang
2010-06-12 14:22 ` [PATCH 3/4] mx51/iomux: add UART and GPIO pad definitions for imx51_3ds board Jason Wang
2010-06-12 14:22 ` [PATCH 4/4] mxc/iomux: add GPIO bank offset for iomux v3 platforms Jason Wang
2010-06-16 6:47 ` [PATCH 0/4]Refine iomux files for i.MX51 Sascha Hauer
2010-06-16 11:08 ` Amit Kucheria
2010-06-17 13:34 ` jason
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=1276352559-8105-1-git-send-email-jason77.wang@gmail.com \
--to=jason77.wang@gmail.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).