From: Wolfram Sang <w.sang@pengutronix.de>
To: Troy Kisky <troy.kisky@boundarydevices.com>
Cc: Hong-Xing.Zhu@freescale.com, cjb@laptop.org,
linux-mmc@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH 1/2] mmc: sdhci-esdhc: simplify cd_gpio, wp_gpio
Date: Sun, 3 Jul 2011 10:22:28 +0200 [thread overview]
Message-ID: <20110703082228.GA22711@pengutronix.de> (raw)
In-Reply-To: <1309562019-32707-1-git-send-email-troy.kisky@boundarydevices.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Fri, Jul 01, 2011 at 04:13:38PM -0700, Troy Kisky wrote:
> Currently, platform data is referenced by non init functions.
> Copy these fields into locally defined struct pltfm_imx_data.
>
> The code also currently frees imx_data on troubles with
> cd_gpio, but returns 0 anyway. Now the code ignores cd_gpio
> and wp_gpio if the values cause an error.
>
> Also, allow mx51/mx53 to use platform data.
>
> Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
Have you seen this series from Shawn?
[PATCH v4 0/4] Extend sdhci-esdhc-imx card_detect and write_protect support for mx5
I haven't checked if you are doing the same or similar, just that you are
changing the same code. Please CC Shawn Guo and Richard Zhu if there is another
patch series needed.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-07-03 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 23:13 [PATCH 1/2] mmc: sdhci-esdhc: simplify cd_gpio, wp_gpio Troy Kisky
2011-07-01 23:13 ` [PATCH 2/2] mmc: sdhci-esdhc: OR mmc->caps with platform data caps Troy Kisky
2011-07-03 8:22 ` Wolfram Sang [this message]
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=20110703082228.GA22711@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Hong-Xing.Zhu@freescale.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=troy.kisky@boundarydevices.com \
/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