From: Arnd Bergmann <arnd@arndb.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] hpet header sanitization
Date: Wed, 22 Mar 2006 23:45:44 +0100 [thread overview]
Message-ID: <200603222345.45718.arnd@arndb.de> (raw)
In-Reply-To: <20060322111446.GA7675@turing.informatik.uni-halle.de>
On Wednesday 22 March 2006 12:14, Clemens Ladisch wrote:
> There isn't any program (except the example in the docs) that uses any
> of these ioctls, and I'm writing patches to make this device available
> through portable timer APIs like hrtimer/POSIX clocks/ALSA that are much
> easier to use besides, so I think it would be a good idea to just
> schedule these ioctls for removal.
Ok, in that case I guess all of the header file should be wrapped inside
#ifdef __KERNEL__. Until now it was not possible to include that header
file in order to get the ioctl definition. It would be somewhat
counterproductive to schedule the user interface for removal while at
the same time making it easier to use it.
Also, I don't see any user of the ioctl function in the kernel, although
it's exported. Are there any out-of-tree users?
Arnd <><
next prev parent reply other threads:[~2006-03-22 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 22:46 [PATCH] hpet header sanitization Randy.Dunlap
2006-03-22 0:13 ` Andrew Morton
2006-03-22 0:26 ` Randy.Dunlap
2006-03-22 9:02 ` Arjan van de Ven
2006-03-22 17:26 ` Randy.Dunlap
2006-03-22 20:08 ` Arjan van de Ven
2006-03-22 20:55 ` Randy.Dunlap
2006-03-22 10:18 ` Arnd Bergmann
2006-03-22 11:14 ` Clemens Ladisch
2006-03-22 17:01 ` Randy.Dunlap
2006-03-23 10:18 ` Clemens Ladisch
2006-03-22 22:45 ` Arnd Bergmann [this message]
2006-03-23 8:13 ` Arjan van de Ven
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=200603222345.45718.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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