public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Petr Baudis <pasky@suse.cz>, Len Brown <lenb@kernel.org>
Subject: Re: /usr/include/*/acpi.h
Date: Thu, 04 Jan 2007 17:36:03 -0600	[thread overview]
Message-ID: <459D8F63.2020504@shaw.ca> (raw)
In-Reply-To: <fa.idYO1X1bcDlMl56ySVF7wfk6M2w@ifi.uio.no>

Petr Baudis wrote:
> On Thu, Jan 04, 2007 at 04:15:45PM CET, Len Brown wrote:
>>>> This header files are part of the linux kernel, and thus of course
>>>> available in /usr/include/{asm,linux}.
>> So you pick up all of the kernel include/linux and include/asm*?
>> (but exclude include/acpi/, which is as much a kernel header as the above)
> 
> Yes, we do not exclude any files from the kernel headers package, since
> it is safer to have an extra file there than miss something that
> something in userspace *could* need - or that is not needed now but can
> silently become useful for something userspace in the future. An "all
> headers part of the linux kernel" is much safer definition than "a
> somewhat random selection of kernel headers".

I wouldn't agree with this. We have what headers are to be used in 
userspace now well defined with the "make headers_install" feature in 
the kernel, which is what Fedora Core 6 is basing its kernel headers on. 
Including all headers is simply asking for userspace to use functions, 
etc. from the kernel source which they have no business using.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-01-04 23:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.qisIxqOea5Rsp26DInWsJ/rJdnQ@ifi.uio.no>
     [not found] ` <fa.5repfGqmg59Vyd5d2/q/VejxXRQ@ifi.uio.no>
     [not found]   ` <fa.hncOoCGnx5UaIfEWQxbz2N/cObM@ifi.uio.no>
     [not found]     ` <fa.ATh7MHfuzpd38JCq6srljq+wqOk@ifi.uio.no>
     [not found]       ` <fa.idYO1X1bcDlMl56ySVF7wfk6M2w@ifi.uio.no>
2007-01-04 23:36         ` Robert Hancock [this message]
     [not found] <200701031552.37919.lenb@kernel.org>
     [not found] ` <20070104104945.GA31430@suse.de>
     [not found]   ` <459CDEB0.5040302@linux.intel.com>
2007-01-04 15:15     ` /usr/include/*/acpi.h Len Brown
2007-01-04 15:48       ` /usr/include/*/acpi.h Petr Baudis

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=459D8F63.2020504@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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