From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Alex Dubov <oakad@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmc: correct semantics of the mmc_host_remove
Date: Sat, 20 Jan 2007 11:21:13 +0100 [thread overview]
Message-ID: <45B1ED19.30000@drzeus.cx> (raw)
In-Reply-To: <859705.85986.qm@web36713.mail.mud.yahoo.com>
Alex Dubov wrote:
>
> Indeed, I may be out of sync on this. Simply, I have this rather ugly hack in the tifm_sd remove
> code which I was forced to add because of the issue in question.
> I'll do some tests with newer kernels then.
>
>
Please do. And if you see a problem, please try to figure out who it is
accessing the device.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-01-20 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 15:04 [PATCH 2.6.19] mmc: Fix handling of response types in imxmmc and tifm drivers Philip Langdale
2007-01-07 17:34 ` Pavel Pisa
2007-01-10 19:02 ` Pierre Ossman
2007-01-19 1:50 ` mmc: correct semantics of the mmc_host_remove Alex Dubov
2007-01-19 8:47 ` Pierre Ossman
2007-01-20 3:46 ` Alex Dubov
2007-01-20 10:21 ` Pierre Ossman [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=45B1ED19.30000@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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