From: zhangfei.gao@gmail.com (zhangfei gao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] provide sdhci driver for mmp2 and pxa910
Date: Fri, 3 Jun 2011 17:48:50 +0800 [thread overview]
Message-ID: <BANLkTikP72ybaqa8zDgNjBQg8Q6SH5fMdw@mail.gmail.com> (raw)
v2->v3, modify according to Arnd and Philip suggestion.
Here are patches to provide separate sdhci driver for mmp2 and pxa910
based on sdhci-platfm.
Rename to sdhci-pxav3.c and sdhci-pxav2.c
Remove sdhci-pxa.c, which is used to share among pxa serious, since
under this method, platform difference have to be put under arch/arm,
which is not easy to track.
As a result, mmp2 mmc resource should be updated accordingly.
next reply other threads:[~2011-06-03 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 9:48 zhangfei gao [this message]
2011-06-03 16:20 ` [PATCH v3 0/3] provide sdhci driver for mmp2 and pxa910 Arnd Bergmann
2011-06-07 5:26 ` zhangfei gao
2011-06-03 21:08 ` Philip Rakity
2011-06-07 5:44 ` zhangfei gao
2011-06-07 7:00 ` Arnd Bergmann
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=BANLkTikP72ybaqa8zDgNjBQg8Q6SH5fMdw@mail.gmail.com \
--to=zhangfei.gao@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).