public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-ia64@vger.kernel.org
Subject: Re: + git-hdrcleanup-vs-git-klibc-on-ia64-2.patch added to -mm tree
Date: Sun, 14 May 2006 22:34:34 +0000	[thread overview]
Message-ID: <4467B07A.5010006@zytor.com> (raw)
In-Reply-To: <1147633985.2551.14.camel@shinybook.infradead.org>

David Woodhouse wrote:
> On Sun, 2006-05-14 at 15:03 -0700, H. Peter Anvin wrote:
>> Keep in mind that userland isn't necessarily glibc.  In particular,
>> for klibc it would be a pain in the arse to have two largely identical
>> copies of the same header file in the kernel tree.
> 
> You can still use the copy from the kernel tree even if we don't
> actually copy it out in 'make headers_install'.
> 
> But yes, this is one of the reasons I haven't touched elf.h (yet).

I could, but that would defeat the purpose somewhat.

I believe "make headers_install" isn't "this is what userspace *has* to 
get from the kernel" (which is, after all, the null set -- people wrote 
C libraries for DOS for example), but "this is what the kernel provides 
to userspace."  It's up to userspace to use it or not, depending on the 
suitability for any one particular userspace.

	-hpa

  parent reply	other threads:[~2006-05-14 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 19:13 + git-hdrcleanup-vs-git-klibc-on-ia64-2.patch added to -mm tree David Woodhouse
2006-05-14 21:13 ` Andreas Schwab
2006-05-14 21:17 ` Christoph Hellwig
2006-05-14 21:37 ` David Woodhouse
2006-05-14 22:03 ` H. Peter Anvin
2006-05-14 22:05 ` H. Peter Anvin
2006-05-14 22:11 ` David Woodhouse
2006-05-14 22:34 ` H. Peter Anvin [this message]
2006-05-14 22:41 ` David Woodhouse
2006-05-14 23:22 ` H. Peter Anvin
2006-05-14 23:35 ` 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=4467B07A.5010006@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-ia64@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