From: David Strobach <lalochcz@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org, Greg KH <greg@kroah.com>,
horms@verge.net.au, damm@opensource.se,
Andrei Warkentin <andreiw@motorola.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: kernel 2.6.38.6 MMC controller problem (fwd)
Date: Mon, 16 May 2011 18:29:31 +0200 [thread overview]
Message-ID: <BANLkTincFDejwEv1zs1V9-kxA-xwUxpbVw@mail.gmail.com> (raw)
In-Reply-To: <m38vu6k5b0.fsf@pullcord.laptop.org>
On Mon, May 16, 2011 at 17:56, Chris Ball <cjb@laptop.org> wrote:
> Also, perhaps you could confirm that setting CONFIG_MMC_CLKGATE=n
> makes all of the problems go away, even with the bad patch applied?
Confirmed. No problem with CONFIG_MMC_CLKGATE=n
David
next prev parent reply other threads:[~2011-05-16 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 7:06 kernel 2.6.38.6 MMC controller problem (fwd) Guennadi Liakhovetski
[not found] ` <BANLkTinbJfDLp5nfkq-VTYLJvihT1thXvA@mail.gmail.com>
2011-05-16 8:42 ` David Strobach
2011-05-16 8:45 ` Guennadi Liakhovetski
2011-05-16 10:26 ` Jaehoon Chung
2011-05-16 10:39 ` Guennadi Liakhovetski
2011-05-16 10:48 ` Jaehoon Chung
2011-05-16 14:52 ` Chris Ball
2011-05-16 15:15 ` David Strobach
2011-05-16 15:56 ` Chris Ball
2011-05-16 16:07 ` Guennadi Liakhovetski
2011-05-16 16:37 ` Chris Ball
2011-05-16 16:42 ` Guennadi Liakhovetski
2011-05-16 17:56 ` Linus Walleij
2011-05-17 9:20 ` Dong, Chuanxiao
2011-05-18 5:29 ` Linus Walleij
2011-05-18 6:01 ` Dong, Chuanxiao
2011-05-16 16:07 ` David Strobach
2011-05-16 16:29 ` David Strobach [this message]
2011-05-18 13:29 ` David Strobach
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=BANLkTincFDejwEv1zs1V9-kxA-xwUxpbVw@mail.gmail.com \
--to=lalochcz@gmail.com \
--cc=andreiw@motorola.com \
--cc=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=greg@kroah.com \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.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).