From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, clemens@ladisch.de
Subject: Re: [PATCH] hpet header sanitization
Date: Wed, 22 Mar 2006 09:26:49 -0800 [thread overview]
Message-ID: <20060322092649.d967c47a.rdunlap@xenotime.net> (raw)
In-Reply-To: <1143018140.2955.45.camel@laptopd505.fenrus.org>
On Wed, 22 Mar 2006 10:02:19 +0100 Arjan van de Ven wrote:
> On Tue, 2006-03-21 at 16:26 -0800, Randy.Dunlap wrote:
> > On Tue, 21 Mar 2006 16:13:03 -0800 Andrew Morton wrote:
> >
> > > "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> > > >
> > > > From: Randy Dunlap <rdunlap@xenotime.net>
> > > >
> > > > Add __KERNEL__ block.
> > > > Use __KERNEL__ to allow ioctl interface to be usable.
> > >
> > > hm, why?
> >
> > because there is a test/example source file in (inside)
> > Documentation/hpet.txt that won't build otherwise.
> > And because hpet.h contains _userspace_ ioctl interface struct
> > and macros...
>
>
> then please split the header in 2 parts; one for the kernel
> and one for userspace
so would you tell me what the purpose (use) of __KERNEL__
is meant to be, please?
Fortunately there are only about 165 header files in include/
that use both __KERNEL__ and _IO() macros (out of 5425 header
files).
> either put both here, or move the kernel one to the directory where the
> source code is
---
~Randy
next prev parent reply other threads:[~2006-03-22 17:24 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 [this message]
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
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=20060322092649.d967c47a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox