From: Wolfram Sang <w.sang@pengutronix.de>
To: "Eric Bénard" <eric@eukrea.com>
Cc: joancarles <joancarles@fqingenieria.es>,
Zhu Richard-R65037 <r65037@freescale.com>,
shawn.guo@linaro.org, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [MX25][MMC] mmc esdhc failure in 3.3
Date: Tue, 27 Mar 2012 11:36:44 +0200 [thread overview]
Message-ID: <20120327093644.GD6790@pengutronix.de> (raw)
In-Reply-To: <20120327112342.73a85a1b@eb-e6520>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
> well I should have said "enough extensive" tests as I did a lot of tests
> on the 3 archs (i.MX25, i.MX35 and i.MX51). What I see here is that on
> i.MX35 and i.MX51 the problem is very easy to reproduce without
> extensive tests (card not detected) and that on i.MX25 it needs more
> tests as the card is properly detected.
Ah, okay, thanks for the clarification! Well, since you retested now and
found it is harder to trigger that could explain why nobody reported it
and why 2.6.39 seems to work (although it maybe doesn't). Thanks for
rechecking. If you submit the patch, you can add my
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Best regards.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-27 9:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:29 [MX25][MMC] mmc esdhc failure in 3.3-rc5 joancarles
2012-03-12 13:12 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 (still present in rc7) joancarles
2012-03-12 13:24 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 Wolfram Sang
2012-03-12 14:50 ` joancarles
2012-03-12 21:45 ` Wolfram Sang
2012-03-13 11:20 ` joancarles
2012-03-13 5:55 ` Zhu Richard-R65037
2012-03-16 15:03 ` joancarles
2012-03-27 7:32 ` [MX25][MMC] mmc esdhc failure in 3.3 joancarles
2012-03-27 7:59 ` joancarles
2012-03-27 8:12 ` Eric Bénard
2012-03-27 8:46 ` joancarles
2012-03-27 8:58 ` Eric Bénard
2012-03-27 13:03 ` Zhu Richard-R65037
2012-03-27 9:01 ` Wolfram Sang
2012-03-27 9:06 ` Eric Bénard
2012-03-27 9:14 ` Wolfram Sang
2012-03-27 9:23 ` Eric Bénard
2012-03-27 9:36 ` Wolfram Sang [this message]
2012-03-27 9:33 ` joancarles
2012-03-27 9:40 ` Eric Bénard
2012-03-27 10:56 ` joancarles
2012-03-28 9:26 ` joancarles
2012-03-28 14:01 ` joancarles
2012-03-27 9:45 ` Wolfram Sang
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=20120327093644.GD6790@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=eric@eukrea.com \
--cc=joancarles@fqingenieria.es \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=r65037@freescale.com \
--cc=shawn.guo@linaro.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