public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@lifl.fr>
To: Jim Nance <jlnance@sdf.lonestar.org>
Cc: Peter Staubach <staubach@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel header policy
Date: Tue, 12 Jul 2005 21:08:53 +0200	[thread overview]
Message-ID: <42D41545.7040809@lifl.fr> (raw)
In-Reply-To: <20050712183859.GA21230@SDF.LONESTAR.ORG>

12.07.2005 20:38, Jim Nance wrote/a écrit:
> 
> 
> Perhaps a little history would help.  In the beginning, the kernel was
> written with the intention that userland would be including the headers.
> And libc did include the kernel headers.
> 
> This did provide an effective way to get new kernel features to show
> up in userland, but it created all sorts of other problems.  Eventually
> it was decided/decreed that userland would NOT include kernel headers.
> Instead, libc would provide a set of headers which would either be
> compatable, or would marshel data into the form the kernel wanted.
>  

So does this mean that all the "#ifdef __KERNEL__" are useless or are 
they still used?

Eric

  reply	other threads:[~2005-07-12 19:09 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
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 [this message]
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=42D41545.7040809@lifl.fr \
    --to=eric.piel@lifl.fr \
    --cc=jlnance@sdf.lonestar.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staubach@redhat.com \
    /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