linux-kernel - Re: feature-removal-schedule obsoletes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45588C0F.60002@drzeus.cx>
Date:	Mon, 13 Nov 2006 16:15:27 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Christoph Hellwig <hch@....de>
CC:	Arnd Bergmann <arnd@...db.de>, Jiri Slaby <jirislaby@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Dominik Brodowski <linux@...do.de>,
	Harald Welte <laforge@...filter.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: feature-removal-schedule obsoletes

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/