public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
	axboe@suse.de, schilling@fokus.fraunhofer.de,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel includefile bug not fixed after a year :-(
Date: Tue, 30 Sep 2003 18:10:18 +0200	[thread overview]
Message-ID: <20030930161018.GA900@mars.ravnborg.org> (raw)
In-Reply-To: <20030930052337.444fdac4.davem@redhat.com>

On Tue, Sep 30, 2003 at 05:23:37AM -0700, David S. Miller wrote:
> 
> Suggest changes to fix the problems, but just saying "don't include
> kernel header in your user apps, NYAH NYAH NYAH!" does not help
> anyone at all.

I really liked the proposal that Matthew Wilcox came up with:

Todays hirachi:
include/linux		=>	Kernel wide internal
include/sub-system	=>	sub-system internal
include/asm-$(ARCH)	=>	arch specific
include/asm		=>	symlink to include/asm-$(ARCH)
include/asm-generic	=>	default arch implementations

Additional hirachy:
usr/include/linux-abi	=>	kernel wide ABI
usr/include/abi-$(ARCH)	=>	arch specifics ABI
usr/include/arch-abi	=>	symlink to above

I've lost the original email, so the names differ, but the
principle is the same.

Then we could slowly migrate the user level stuff to usr/include.
Do you see this as a sensible solution also for ipv6?

	Sam

  parent reply	other threads:[~2003-09-30 16:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 11:44 Kernel includefile bug not fixed after a year :-( Joerg Schilling
2003-09-30 11:54 ` Jens Axboe
2003-09-30 12:12   ` Andreas Steinmetz
2003-09-30 12:21     ` Jens Axboe
2003-09-30 12:26       ` Andreas Steinmetz
2003-09-30 12:30         ` Jens Axboe
2003-09-30 12:32       ` David S. Miller
2003-09-30 12:40         ` Jens Axboe
2003-09-30 12:39           ` David S. Miller
2003-09-30 12:23     ` David S. Miller
2003-09-30 12:28       ` Jens Axboe
2003-09-30 12:34         ` David S. Miller
2003-09-30 12:42           ` Jens Axboe
2003-09-30 19:09         ` Erik Andersen
2003-10-01  8:48           ` Paul Rolland
2003-10-01  8:55             ` Arjan van de Ven
2003-10-01 17:49             ` Erik Andersen
2003-09-30 16:10       ` Sam Ravnborg [this message]
2003-10-01  6:39         ` David S. Miller
2003-10-02  6:42         ` Eric W. Biederman
2003-09-30 19:04       ` Erik Andersen
2003-09-30 12:25     ` Nick Piggin
2003-09-30 19:00     ` Erik Andersen
2003-10-01  8:47       ` Paul Rolland
  -- strict thread matches above, loose matches on Subject: below --
2003-10-01  1:05 Albert Cahalan
2003-09-30 13:26 Joerg Schilling
2003-09-30 12:52 Joerg Schilling
2003-09-30 12:37 Joerg Schilling
2003-09-30 13:21 ` Tomas Szepe
2003-09-30 11:57 Joerg Schilling
2003-09-30 12:06 ` Jens Axboe
2003-09-30 12:28   ` David S. Miller
2003-09-30 12:38     ` Jens Axboe
2003-09-30 14:41       ` Krzysztof Halasa
2003-10-10  6:36     ` Sandy Harris
2003-09-30 10:28 Joerg Schilling
2003-09-30 11:05 ` Jens Axboe

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=20030930161018.GA900@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ast@domdv.de \
    --cc=axboe@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schilling@fokus.fraunhofer.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