All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linuxabi@zytor.com, "Chris Friesen" <cfriesen@nortelnetworks.com>,
	"Måns Rullgård" <mru@kth.se>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.3.0
Date: Thu, 04 Mar 2004 11:50:36 -0500	[thread overview]
Message-ID: <40475E5C.9020708@pobox.com> (raw)
In-Reply-To: <m3u115zxif.fsf@defiant.pm.waw.pl>

Krzysztof Halasa wrote:
> Sam Ravnborg <sam@ravnborg.org> writes:
> 
> 
>>IIRC the current agreed scheme is something along the lines of this:
>>
>>abi/abi-linux/* Userspace relevant parts of include/linux
>>abi/abi-asm/ symlink to abi/abi-$(ARCH)
>>abi/abi-i386 i386 specific userland abi
>>abi/abi-ppc  ppc ....
> 
> 
> More efforts, no real effects.
> I don't think we need such an infrastructure.
> The normal headers should just be usable for user-space inclusion.

No, this is a big pain :)

The ABI headers shared with userspace need to be split from definitions 
that are only used in kernel space.  #ifdef __KERNEL__ is a source of 
frustration :)

	Jeff




  reply	other threads:[~2004-03-04 16:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 18:42 [ANNOUNCE] linux-libc-headers 2.6.3.0 Mariusz Mazur
2004-02-29 20:19 ` H. Peter Anvin
2004-02-29 20:30   ` Mariusz Mazur
2004-02-29 21:03     ` H. Peter Anvin
2004-02-29 21:21       ` Mariusz Mazur
2004-02-29 21:33         ` Måns Rullgård
2004-03-01 14:42           ` Chris Friesen
2004-03-01 18:10             ` Krzysztof Halasa
2004-03-03 12:49               ` Måns Rullgård
2004-03-03 15:22               ` Sam Ravnborg
2004-03-03 16:49                 ` Krzysztof Halasa
2004-03-04 16:50                   ` Jeff Garzik [this message]
2004-03-04 18:49                     ` [Linuxabi] " H. Peter Anvin
2004-03-04  4:43                 ` [Linuxabi] " H. Peter Anvin
2004-03-03 18:08               ` [ANNOUNCE] " Mariusz Mazur
2004-03-03 19:20                 ` Grzegorz Kulewski
2004-03-04 14:13                 ` Krzysztof Halasa
2004-03-04 20:49                   ` Mariusz Mazur
2004-03-04 21:27                     ` Chris Friesen
2004-03-04 22:52                       ` Mariusz Mazur
2004-03-04 23:32                         ` Chris Friesen
2004-03-05 17:02                     ` Krzysztof Halasa
2004-03-05 23:44                       ` Grzegorz Kulewski
2004-03-06 22:30                         ` Krzysztof Halasa
2004-03-07  1:15                           ` Paul Jackson
2004-03-07 19:00                             ` Krzysztof Halasa
2004-03-08  1:28                               ` Paul Jackson
2004-03-08 15:03                                 ` Krzysztof Halasa
2004-03-08 15:37                                   ` Chris Friesen
2004-03-08 20:27                                     ` Krzysztof Halasa
2004-02-29 21:25     ` Benjamin Herrenschmidt

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=40475E5C.9020708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxabi@zytor.com \
    --cc=mru@kth.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.