public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andries.Brouwer@cwi.nl, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linuxabi
Date: Fri, 3 Oct 2003 19:32:51 +0200	[thread overview]
Message-ID: <20031003173251.GA2097@mars.ravnborg.org> (raw)
In-Reply-To: <m17k3nhfex.fsf@ebiederm.dsl.xmission.com>

On Thu, Oct 02, 2003 at 08:39:50AM -0600, Eric W. Biederman wrote:
> So all of the definitions exported
> through linuxabi need to be in a linux centric namespace.

What we try to achieve is to use the same headerfiles for user,
and kernel. Previously this has been done by including selected
files direct from include/linux/*.
A few cases that I recall is DVB, scsi, and ipv6.
For all of these there were no need to create a specific linux namespace.
If there is parts of the kernel that _really_ require a separate
linux namespace then we need to find a solution for that part.
But we should not try to uglify the interface becasue a limited
part of the kernel interface have specific needs.

And since dvb, scsi and ipv6 could accept current namespace before,
they should also be able to accept it today - no?

The concept introduced by inventing abi/ is to make it visible
what part of the kernel interface is actually visible from user level.
And also a good way for us to make sure no kernel specific types sneaks in.

	Sam

  parent reply	other threads:[~2003-10-03 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  0:01 [PATCH] linuxabi Andries.Brouwer
2003-10-01  2:05 ` Bernd Eckenfels
2003-10-01  3:34   ` viro
2003-10-01  4:52     ` H. Peter Anvin
2003-10-01  5:22       ` Philippe Troin
2003-10-01  5:50         ` Miles Bader
2003-10-01 14:33     ` Daniel Jacobowitz
2003-10-01 10:20 ` J.A. Magallon
2003-10-02 14:39 ` Eric W. Biederman
2003-10-02 15:33   ` Andries Brouwer
2003-10-03  7:36     ` Eric W. Biederman
2003-10-04  3:37       ` Rob Landley
2003-10-04  6:31         ` Erik Andersen
     [not found]   ` <fa.e2g5r6g.u3igb4@ifi.uio.no>
2003-10-03 16:49     ` Kai Henningsen
2003-10-03 17:32   ` Sam Ravnborg [this message]
     [not found] <BCSP.62t.7@gated-at.bofh.it>
     [not found] ` <CcWl.7kh.9@gated-at.bofh.it>
     [not found]   ` <CdIL.8ts.13@gated-at.bofh.it>
2003-10-03 14:02     ` Ihar 'Philips' Filipau

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=20031003173251.GA2097@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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