From: Avi Kivity <avi@argo.co.il>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Hans-Jürgen Koch" <hjk@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: Userspace I/O driver core
Date: Thu, 14 Dec 2006 15:38:59 +0200 [thread overview]
Message-ID: <458153F3.4040203@argo.co.il> (raw)
In-Reply-To: <Pine.LNX.4.61.0612141338490.6223@yvahk01.tjqt.qr>
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
next prev parent reply other threads:[~2006-12-14 13:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 1:06 Userspace I/O driver core Greg KH
2006-12-14 5:48 ` Ben Nizette
2006-12-14 9:44 ` Avi Kivity
2006-12-14 10:19 ` Arjan van de Ven
2006-12-14 10:46 ` Avi Kivity
2006-12-14 10:54 ` Arjan van de Ven
2006-12-14 10:56 ` Avi Kivity
2006-12-14 17:54 ` Greg KH
2006-12-16 14:48 ` Dr. David Alan Gilbert
2006-12-14 10:25 ` Hans-Jürgen Koch
2006-12-14 10:48 ` Avi Kivity
2006-12-14 12:39 ` Jan Engelhardt
2006-12-14 13:38 ` Avi Kivity [this message]
2006-12-14 17:48 ` Jan Engelhardt
2006-12-14 18:00 ` Greg KH
2006-12-14 10:52 ` Alan
2006-12-14 11:22 ` Thomas Gleixner
2006-12-14 11:39 ` Alan
2006-12-14 11:37 ` Hans-Jürgen Koch
2006-12-14 12:45 ` Alan
2006-12-14 12:37 ` Jan Engelhardt
2006-12-14 16:10 ` linux-os (Dick Johnson)
2006-12-14 21:55 ` Ben Nizette
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=458153F3.4040203@argo.co.il \
--to=avi@argo.co.il \
--cc=hjk@linutronix.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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 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.