From: b29396@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] mmc: sdhci-esdhc-imx: eliminate enum imx_esdhc_type
Date: Fri, 18 Oct 2013 16:09:23 +0800 [thread overview]
Message-ID: <20131018080922.GC22289@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <1381994387-9656-1-git-send-email-shawn.guo@linaro.org>
On Thu, Oct 17, 2013 at 03:19:43PM +0800, Shawn Guo wrote:
> Changes since v1:
> * Create flags only for features and errata such things, and keep using
> is_imx*_esdhc() for small register differences between esdhc variants.
>
> Shawn Guo (4):
> mmc: sdhci-esdhc-imx: add flag ESDHC_FLAG_ENGCM07207
> mmc: sdhci-esdhc-imx: add flag ESDHC_FLAG_USDHC
> mmc: sdhci-esdhc-imx: pdev->id_entry should be immutable
> mmc: sdhci-esdhc-imx: create struct esdhc_soc_data
>
> drivers/mmc/host/sdhci-esdhc-imx.c | 126 +++++++++++++++++++-----------------
> 1 file changed, 68 insertions(+), 58 deletions(-)
>
> --
> 1.7.9.5
>
Acked-by: Dong Aisheng <b29396@freescale.com>
I will rebase my mx6sl std tuning patch series based on it
and send out again.
Regards
Dong Aisheng
next prev parent reply other threads:[~2013-10-18 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 7:19 [PATCH v2 0/4] mmc: sdhci-esdhc-imx: eliminate enum imx_esdhc_type Shawn Guo
2013-10-17 7:19 ` [PATCH v2 1/4] mmc: sdhci-esdhc-imx: add flag ESDHC_FLAG_ENGCM07207 Shawn Guo
2013-10-17 7:19 ` [PATCH v2 2/4] mmc: sdhci-esdhc-imx: add flag ESDHC_FLAG_USDHC Shawn Guo
2013-10-17 7:19 ` [PATCH v2 3/4] mmc: sdhci-esdhc-imx: pdev->id_entry should be immutable Shawn Guo
2013-10-17 7:19 ` [PATCH v2 4/4] mmc: sdhci-esdhc-imx: create struct esdhc_soc_data Shawn Guo
2013-10-18 8:09 ` Dong Aisheng [this message]
2013-10-21 2:10 ` [PATCH v2 0/4] mmc: sdhci-esdhc-imx: eliminate enum imx_esdhc_type Chris Ball
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=20131018080922.GC22289@shlinux2.ap.freescale.net \
--to=b29396@freescale.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).