public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: David Miller <davem@davemloft.net>
Cc: dwmw2@infradead.org, arjan@infradead.org,
	linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: 2.6.18 Headers - Long
Date: Fri, 14 Jul 2006 13:57:39 -0700	[thread overview]
Message-ID: <44B80543.4050608@jg555.com> (raw)
In-Reply-To: <20060714.131957.57444250.davem@davemloft.net>

 When I wrote my script to sanitize, I was really surprised on which 
headers gets utilized and which ones didn't.. I have it down to the bare 
minimums in my script.

As far as glibc goes, from my people who are helping me the alpha 
architecture is the culprit there.

Do we have a list of what headers are "user-space" and which ones should 
not be "user-space"?

Also David W, let me know what I can do to help you out, a lot of people 
on my end want to get this working properly.

Who's maintaining util-linux these days, we probably should get a patch 
to them.




  reply	other threads:[~2006-07-14 21:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  0:35 2.6.18 Headers - Long Jim Gifford
2006-07-14  0:25 ` David Woodhouse
2006-07-14  2:18   ` Jim Gifford
2006-07-14 18:55     ` David Woodhouse
2006-07-14 19:28       ` Jim Gifford
2006-07-14 19:39         ` Arjan van de Ven
2006-07-14 20:16           ` David Woodhouse
2006-07-14 20:19             ` David Miller
2006-07-14 20:57               ` Jim Gifford [this message]
2006-07-15  4:33                 ` Randy.Dunlap
2006-07-16 14:08                   ` Nix
2006-07-15  7:19                 ` David Woodhouse
2006-07-15  7:08               ` David Woodhouse
2006-07-14 19:57         ` David Woodhouse
2006-07-14 20:06         ` Erik Andersen
2006-07-14 20:19   ` Christoph Hellwig
2006-08-26 16:09   ` David Woodhouse
2006-08-29 12:25     ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2006-07-15 21:09 Albert Cahalan
2006-07-15 21:19 ` Arjan van de Ven
2006-07-17  5:21   ` Ralf Baechle
2006-07-15 21:44 ` Adrian Bunk
2006-07-15 21:47 ` David Woodhouse
2006-07-16  6:18   ` Albert Cahalan
2006-07-16  6:26     ` Arjan van de Ven
2006-07-16  8:05     ` David Woodhouse
2006-07-16  8:20 ` Jakub Jelinek
2006-07-16 12:34 ` Kyle Moffett
2006-07-16 12:48   ` Russell King
2006-07-16 18:38   ` Albert Cahalan
2006-07-16 18:53     ` Russell King
2006-07-16 19:22       ` Albert Cahalan
2006-07-16 19:41         ` Russell King
2006-07-17  1:26         ` Arjan van de Ven
2006-07-17  1:23   ` David Miller

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=44B80543.4050608@jg555.com \
    --to=maillist@jg555.com \
    --cc=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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