From: Wolfram Sang <w.sang@pengutronix.de>
To: Zhu Richard-R65037 <r65037@freescale.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH 0/2] Add GPIO WP and HW bus-width caps when support i.MX51 BBG board
Date: Wed, 3 Nov 2010 15:06:04 +0100 [thread overview]
Message-ID: <20101103140604.GD4167@pengutronix.de> (raw)
In-Reply-To: <010C9052C42A00499CE76D637FA5EE90A516@039-SN1MPN1-002.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Hi Richard,
> Do you have any comments about the following patches?
> These patches add the GPIO write protection, and add the HW bus-width
> caps limitation.
First patch: The sdhci-part is okay (it's trivial enough), did not check
the iomux-stuff, but I assume it works for you :) If you are basing your
patch on my RFC-patches, it would be better for the process if you'd a)
note the dependency in your patch and b) add some Acked-by or Tested-by
to my original series.
Second patch: There is some discussion about the bus width currently
going on. I'd suggest you join it.
BTW did you try adding regulator support yet?
Best 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:[~2010-11-03 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 10:00 [PATCH 0/2] Add GPIO WP and HW bus-width caps when support i.MX51 BBG board Richard Zhu
2010-10-20 10:00 ` [PATCH 1/2] Add the GPIO Write Protection Solution on " Richard Zhu
2010-10-20 10:00 ` [PATCH 2/2] Add the HW board caps flag for MX51 BBG Richard Zhu
2010-10-20 10:24 ` [PATCH 1/2] Add the GPIO Write Protection Solution on i.MX51 BBG board Baruch Siach
[not found] ` <010C9052C42A00499CE76D637FA5EE90A516@039-SN1MPN1-002.039d.mgd.msft.net>
2010-11-03 14:06 ` 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=20101103140604.GD4167@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-mmc@vger.kernel.org \
--cc=r65037@freescale.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;
as well as URLs for NNTP newsgroup(s).