From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Ian Molton <ian@mnementh.co.uk>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Magnus Damm <damm@opensource.se>
Subject: Re: [PATCH v2] mmc: tmio: fix recursive spinlock, don't schedule with interrupts disabled
Date: Wed, 13 Jul 2011 20:39:42 -0400 [thread overview]
Message-ID: <m2y601u241.fsf@bob.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1107140132040.30737@axis700.grange> (Guennadi Liakhovetski's message of "Thu, 14 Jul 2011 01:33:03 +0200 (CEST)")
Hi Guennadi,
On Wed, Jul 13 2011, Guennadi Liakhovetski wrote:
>> In mmc-next there's a "goto out;" after the mmc_detect_change call, which
>> looks like it's always been there. Am I missing a patch this depends on?
>>
>> (It'd be a good time to get a full set of tmio patches for 3.1 pulled
>> together, if you can do that.)
>
> Ok, if you don't mind, I'll get a couple of hours of sleep, and will reply
> to you first thing in the morning:-)
Not only do I not mind, I'd strongly prefer if you did. ;-)
Thanks very much,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-14 0:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:06 [PATCH] mmc: tmio: fix recursive spinlock, don't schedule with interrupts disabled Guennadi Liakhovetski
2011-06-15 16:50 ` Guennadi Liakhovetski
2011-06-20 16:27 ` [PATCH v2] " Guennadi Liakhovetski
2011-07-12 10:51 ` kuninori.morimoto.gx
2011-07-13 15:00 ` Chris Ball
2011-07-13 23:33 ` Guennadi Liakhovetski
2011-07-14 0:39 ` Chris Ball [this message]
2011-07-14 10:26 ` Guennadi Liakhovetski
2011-07-14 10:12 ` [PATCH v3] " Guennadi Liakhovetski
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=m2y601u241.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@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