mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Linus Torvalds <torvalds@osdl.org>,
	David Woodhouse <dwmw2@infradead.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Simple header cleanups
Date: Thu, 27 Apr 2006 10:49:42 +0200	[thread overview]
Message-ID: <m3fyjze72x.fsf@defiant.localdomain> (raw)
In-Reply-To: <200604271010.06711.vda@ilport.com.ua> (Denis Vlasenko's message of "Thu, 27 Apr 2006 10:10:06 +0300")

Denis Vlasenko <vda@ilport.com.ua> writes:

> Maybe we should have a script which processes kernel's include/linux/*
> files and produces sanitized set of headers (by deleting
> "#ifdef __KERNEL__" blocks, etc), which will be treated at
> *the* official kernel<->userspace API and will be used by glibc etc?

It would really be better to create "ABI/API" header set in the
kernel at last. Glibc people, Linux-only kernel utils and of course
the rest of the kernel could just #include the API files (a copy
probably).

We _do_ have a stable userspace ABI and API, and contrary to the popular
belief the header set would be quite small (probably an order of magnitude
smaller than the "sanitized headers" package). What we need to export is
the actual API (including things like ioctl, netlink, SG_IO etc), most
things should be kept private to the kernel (and never copied anywhere
etc).

I realize this is completely uninteresting job. Perhaps someone wants
to pay a bit for having done it?

Why do we need, for example, /usr/include/linux/sc26198.h (FC5's
glibc-kernheaders-3.0-5.2)?

 *      sc26198.h  -- SC26198 UART hardware info.
...
/*
 *      Global register definitions. These registers are global to each 26198
 *      device, not specific ports on it.
 */
#define TSTR            0x0d
#define GCCR            0x0f
#define ICR             0x1b
-- 
Krzysztof Halasa

  parent reply	other threads:[~2006-04-27  8:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  2:13 David Woodhouse
2006-04-27  2:18 ` Linus Torvalds
2006-04-27  2:27   ` Gerrit Huizenga
2006-04-27  2:46     ` Linus Torvalds
2006-04-27  3:00     ` David Woodhouse
2006-04-27  4:32       ` Gerrit Huizenga
2006-04-27  2:37   ` David Woodhouse
2006-04-27  2:59     ` Linus Torvalds
2006-04-27  3:17       ` David Woodhouse
2006-04-27  3:31         ` Linus Torvalds
2006-04-27  3:41           ` David Woodhouse
2006-04-27  7:10           ` Denis Vlasenko
2006-04-27  7:23             ` Arjan van de Ven
2006-04-27  8:49             ` Krzysztof Halasa [this message]
2006-04-27 11:03               ` Arnd Bergmann
2006-04-27 21:37           ` Adrian Bunk
2006-04-27 22:00             ` Linus Torvalds
2006-04-27 23:11               ` David Woodhouse
2006-04-27 23:12               ` Adrian Bunk
2006-04-28  0:01                 ` Linus Torvalds
2006-04-28  0:55                   ` David Woodhouse
2006-04-28 15:32                   ` Jan Engelhardt
2006-04-28 15:37                     ` David Woodhouse
2006-04-28 15:59                       ` Arjan van de Ven
2006-04-28 16:01                       ` Kyle Moffett
2006-04-29 10:33                         ` Krzysztof Halasa
2006-05-03  2:53                   ` H. Peter Anvin
2006-04-30  9:38               ` Peter Chubb
2006-04-30  9:59                 ` David Woodhouse
2006-04-30 21:48                   ` Peter Chubb
2006-04-27 15:05   ` David Woodhouse

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=m3fyjze72x.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=vda@ilport.com.ua \
    /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

all inboxes | Powered by JetHome®