public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: Header files and the kernel ABI
Date: Thu, 25 Jul 2002 10:00:53 +0200	[thread overview]
Message-ID: <3D3FB035.mailB014KTO5@viadomus.com> (raw)
In-Reply-To: <aho5ql$9ja$1@cesium.transmeta.com>

    Hi HPA :)

>I would like to propose that these files be set up in the #include
>namespace as <linux/abi/*>, with <linux/abi/arch/*> for any
>architecture-specific support files (I do believe, however, that those
>files should only be included by files in the linux/abi/ root.  This
>probably would be a symlink to ../asm/abi in the kernel sources,
>unless we change the kernel include layout.)

    I think this is a *really* great idea. It will solve lots of
problems IMHO. Now the glibc copies some of the kernel headers, and
in the future it will support more, but standarizing an ABI set of
headers will be better (IMHO again). Go for it ;)

    Raúl

  parent reply	other threads:[~2002-07-25  7:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  6:28 Header files and the kernel ABI H. Peter Anvin
2002-07-25  6:51 ` Andreas Dilger
2002-07-25  7:07   ` H. Peter Anvin
2002-07-25  7:32     ` Andreas Dilger
2002-07-25 16:29       ` Oliver Xymoron
2002-07-25 16:31         ` H. Peter Anvin
2002-07-25 18:19           ` Erik Andersen
2002-07-25 20:03             ` Oliver Xymoron
2002-07-27 11:29               ` Eric W. Biederman
2002-07-25 16:30       ` H. Peter Anvin
2002-07-25  8:00 ` DervishD [this message]
2002-07-25 13:08 ` Brad Hards
2002-07-25 16:09   ` DervishD
2002-07-25 16:17   ` H. Peter Anvin
2002-07-25 18:22     ` Erik Andersen
2002-07-31 21:37 ` Kernel ABI BoF at Linux-Kongress? [was: Header files and the kernel ABI] Brad Hards
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 21:13 Header files and the kernel ABI dank
2002-07-26  2:37 ` jw schultz

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=3D3FB035.mailB014KTO5@viadomus.com \
    --to=raul@pleyades.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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