From: Peter Staubach <staubach@redhat.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Marc Aurele La France <tsi@ualberta.ca>, linux-kernel@vger.kernel.org
Subject: Re: Kernel header policy
Date: Tue, 12 Jul 2005 09:26:53 -0400 [thread overview]
Message-ID: <42D3C51D.3020703@redhat.com> (raw)
In-Reply-To: <200507120206.j6C26kGY017571@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
>>I am contacting you to express my concern over a growing trend in kernel
>>development. I am specifically referring to changes being made to kernel
>>headers that break compatibility at the userland level, where __KERNEL__
>>isn't #define'd.
>>
>>
>
>The policy with respect to kernel headers is /very/ simple:
>
> T H E Y A R E N E V E R U S E D F R O M U S E R L A N D.
>
>This general policy makes all your points (trivially) moot.
>
I must admit a little confusion here. Clearly, kernel header files are
used at the user level. The kernel and user level applications must share
definitions for a great many things.
Perhaps more precisely, the rule is that kernel header files should not be
#include'd directly from user level applications, but may be #include'd
indirectly through other header files as appropriate?
Thanx...
ps
next prev parent reply other threads:[~2005-07-12 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 21:37 Kernel header policy Marc Aurele La France
2005-07-11 21:56 ` Stephen Frost
2005-07-11 22:44 ` Tomasz Torcz
2005-07-12 2:06 ` Horst von Brand
2005-07-12 13:26 ` Peter Staubach [this message]
2005-07-12 13:36 ` Arjan van de Ven
2005-07-12 16:30 ` Alistair John Strachan
2005-07-12 18:38 ` Jim Nance
2005-07-12 19:08 ` Eric Piel
2005-07-12 20:18 ` Tom Rini
2005-07-12 3:07 ` Greg KH
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=42D3C51D.3020703@redhat.com \
--to=staubach@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsi@ualberta.ca \
--cc=vonbrand@inf.utfsm.cl \
/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