From: Petr Baudis <pasky@suse.cz>
To: Len Brown <lenb@kernel.org>
Cc: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>,
Thorsten Kukuk <kukuk@suse.de>, Thomas Renninger <trenn@suse.de>,
linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /usr/include/*/acpi.h
Date: Thu, 4 Jan 2007 16:48:28 +0100 [thread overview]
Message-ID: <20070104154828.GH13181@pasky.or.cz> (raw)
In-Reply-To: <200701041015.45525.lenb@kernel.org>
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".
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
-- Kurt Vonnegut, Sirens from Titan
prev parent reply other threads:[~2007-01-04 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 20:52 /usr/include/*/acpi.h Len Brown
2007-01-04 8:45 ` /usr/include/*/acpi.h Thomas Renninger
2007-01-04 10:49 ` /usr/include/*/acpi.h Thorsten Kukuk
2007-01-04 11:02 ` /usr/include/*/acpi.h Alexey Starikovskiy
2007-01-04 15:15 ` /usr/include/*/acpi.h Len Brown
2007-01-04 15:48 ` Petr Baudis [this message]
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=20070104154828.GH13181@pasky.or.cz \
--to=pasky@suse.cz \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=kukuk@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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