public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, clemens@ladisch.de
Subject: Re: [PATCH] hpet header sanitization
Date: Tue, 21 Mar 2006 16:26:30 -0800	[thread overview]
Message-ID: <20060321162630.d995c63c.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060321161303.53c2895f.akpm@osdl.org>

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


> My general approach to __KERNEL__ fixes is to not support new includers of
> kernel headers but to accept patches which fix up existing applications of
> __KERNEL__.
> 
> It's basically a compromise between the
> dont-include-kernel-headers-from-userspace fundamentalists and the
> but-i-want-my-stuff-to-work pragmatists ;)
> 
> But hpet.h never had __KERNEL__, so there's no regression here.
> 
> That being said, it looks like a sensible change - let's see if we can
> sneak it in without the fundies noticing.

---
~Randy

  reply	other threads:[~2006-03-22  0: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 [this message]
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
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=20060321162630.d995c63c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.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