public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Jeff Garzik <jgarzik@pobox.com>,
	"Ihar 'Philips' Filipau" <filia@softhome.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.
Date: Tue, 19 Aug 2003 08:32:24 -0400	[thread overview]
Message-ID: <200308190832.24744.rob@landley.net> (raw)
In-Reply-To: <20030818190421.GN24693@gtf.org>

On Monday 18 August 2003 15:04, Jeff Garzik wrote:

> >    But generally idea is good: keep interface separately from
> > implementation.
>
> No, the idea is to physically separate the headers.
>
> include/{linux,asm} is currently copied to userspace, hacked a bit,
> and then shipped as the "glibc-kernheaders" package.

Or used directly by uclibc (and linux from scratch) to build the library 
against.

> I would rather that the kernel developers directly maintained this
> interface, by updating headers in include/abi, rather than ad-hoc by
> distro people.
>
> 	Jeff

Okay, I'd like to ask about the headers thing:

I've got a project using uclibc, and build it myself, currently against the 
2.4 headers.  What's the plan for 2.6?  Everything I've seen on the subject 
is "using kernel headers directly from userspace is evil, even to build your 
libc against, but we currently offer no alternative, so go bug your libc 
maintainer and have THEM do it..."

I'm hoping I've missed something in the months I was off the list this spring, 
but haven't quite figured out what to search for in the archives yet...

Rob



  reply	other threads:[~2003-08-19 15:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lRjc.6o4.3@gated-at.bofh.it>
     [not found] ` <lRjg.6o4.15@gated-at.bofh.it>
     [not found]   ` <lWLS.39x.5@gated-at.bofh.it>
     [not found]     ` <lWLZ.39x.29@gated-at.bofh.it>
2003-08-18 18:54       ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Ihar 'Philips' Filipau
2003-08-18 19:04         ` Jeff Garzik
2003-08-19 12:32           ` Rob Landley [this message]
2003-08-19 17:26             ` Jeff Garzik
2003-08-19 21:38               ` Will uclibc be supported in 2.6? (was Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.) Rob Landley
2003-08-19 21:47                 ` Jeff Garzik
2003-08-20  1:42               ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Erik Andersen
2003-08-20 23:48             ` Jamie Lokier
2003-08-21  0:02               ` Jeff Garzik
2003-08-22  0:32                 ` Rob Landley
2003-08-22  0:50                   ` Chris Friesen
2003-08-22  1:58                     ` Rob Landley
2003-08-22  0:54                   ` Jeff Garzik
2003-08-18 20:40         ` Sam Ravnborg
2003-08-18 12:36 Andries.Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18 12:19 Andries.Brouwer
2003-08-18 12:24 ` Christoph Hellwig
2003-08-18 18:08   ` Sam Ravnborg
2003-08-18 18:14     ` Jeff Garzik
2003-08-18 15:21 ` Linus Torvalds
2003-08-18 15:32   ` Jeff Garzik
2003-08-18 16:13 ` Patrick Mansfield

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=200308190832.24744.rob@landley.net \
    --to=rob@landley.net \
    --cc=filia@softhome.net \
    --cc=jgarzik@pobox.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