From: jason77.wang@gmail.com (Jason Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/7]Add i.MX51 3-stack board support
Date: Fri, 4 Jun 2010 22:32:50 +0800 [thread overview]
Message-ID: <1275661977-8077-1-git-send-email-jason77.wang@gmail.com> (raw)
It seems that it is failed when sending my V3 patches, now
resend once more.
I don't know why 2 patches([patch 2/3] and [patch 3/3]) are lost in
the V2 review.
In V3, i fix all comments both in V1 and V2.
Big diffs:
1) the number of patches increases from 3 to 7, because i add 1 3ds
common debug board patch, 2 iomux pad rename and update patches and
1 revert mx31_3ds debug board relating stuffs patch.
2) Though the smsc911x_platform_config is a little bit different
between mx31_3ds and mx51_3ds originally, when using the common
configuration in the mxc debug board, they all works fine. I have
validated these two BSPs through mounting NFS rootfs.
3) the patch [3/7] is a rename and cleanup of iomux pad definition,
i don't know if this update has been merged, if so, please drop
it.
next reply other threads:[~2010-06-04 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 14:32 Jason Wang [this message]
2010-06-04 14:32 ` [PATCH V3 1/7] mxc: add common debug board for 3-stack platforms Jason Wang
2010-06-04 14:32 ` [PATCH V3 2/7] mxc/iomux: add GPIO bank offset for iomux v3 platforms Jason Wang
2010-06-04 14:32 ` [PATCH V3 3/7] mx51/iomux: fix some pad names and make some cleanups Jason Wang
2010-06-04 14:32 ` [PATCH V3 4/7] mx51/iomux: add pad definition for mx51_3ds Jason Wang
2010-06-04 14:32 ` [PATCH V3 5/7] mxc/mx51: Add support for the imx51 3-stack board Jason Wang
2010-06-04 14:32 ` [PATCH V3 6/7] mx51/keypad: add keypad support for i.MX51 platforms Jason Wang
2010-06-04 14:32 ` [PATCH V3 7/7] mx31_3ds: revert cpld debug board relate code Jason Wang
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=1275661977-8077-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).