From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Christoph Hellwig <hch@lst.de>
Cc: Arnd Bergmann <arnd@arndb.de>, Jiri Slaby <jirislaby@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>, Dominik Brodowski <linux@brodo.de>,
Harald Welte <laforge@netfilter.org>,
Arjan van de Ven <arjan@infradead.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: feature-removal-schedule obsoletes
Date: Mon, 13 Nov 2006 16:15:27 +0100 [thread overview]
Message-ID: <45588C0F.60002@drzeus.cx> (raw)
In-Reply-To: <20061028105755.GA20103@lst.de>
Christoph Hellwig wrote:
> On Sat, Oct 28, 2006 at 10:34:51AM +0200, Pierre Ossman wrote:
>
>> What should be used to replace it? The MMC block driver uses it to
>> manage the block device queue. I am not that intimate with the block
>> layer so I do not know the proper fix.
>>
>
> kthread_create/kthread_run. Here's a draft patch (and it's against
> a rather old tree and untested due to lack of hardware so it really
> should be considered just a draft).
>
>
Patch looks ok to me and seems to work fine. Are you willing to sign off
on it?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2006-11-13 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 14:32 feature-removal-schedule obsoletes Jiri Slaby
2006-10-15 15:05 ` Jean Delvare
2006-10-16 13:33 ` Christoph Hellwig
2006-10-24 19:24 ` Arnd Bergmann
2006-10-24 19:28 ` Adrian Bunk
2006-10-24 20:55 ` Jörn Engel
2006-10-28 8:34 ` Pierre Ossman
2006-10-28 10:06 ` Arnd Bergmann
2006-10-28 10:57 ` Christoph Hellwig
2006-11-13 15:15 ` Pierre Ossman [this message]
2006-11-13 18:22 ` Christoph Hellwig
2006-10-31 15:57 ` Jörn Engel
2006-10-31 19:32 ` Russell King
2006-10-31 21:41 ` Jörn Engel
2006-10-31 20:20 ` Pierre Ossman
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=45588C0F.60002@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=arjan@infradead.org \
--cc=arnd@arndb.de \
--cc=bunk@stusta.de \
--cc=hch@lst.de \
--cc=jirislaby@gmail.com \
--cc=khali@linux-fr.org \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.