linux-kernel - Re: Userspace I/O driver core

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: <458153F3.4040203@argo.co.il>
Date:	Thu, 14 Dec 2006 15:38:59 +0200
From:	Avi Kivity <avi@...o.co.il>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
CC:	Hans-Jürgen Koch <hjk@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Userspace I/O driver core

Jan Engelhardt wrote:
>> It has to be written once, but compiled for every kernel
>> version and $arch out there (for out of tree drivers), or it
>> has to wait for the next kernel release and distro sync (for
>> in-tree drivers).
>>     
>
> Still better than written for every _and_ compiled for every.
> But wait, make it simpler: just give the source to the user and
> don't bother with precompiling. It's such a PITA anyhow.
>   

Users don't compile.  They use.  That's why they're called users.

And please don't suggest wrapper scripts to do the compilation.


-- 
error compiling committee.c: too many arguments to function

-
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/