All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, klibc@zytor.com
Subject: Re: [klibc] [patch] import socket defines
Date: Thu, 10 Jan 2008 23:42:28 -0800	[thread overview]
Message-ID: <47871DE4.40906@zytor.com> (raw)
In-Reply-To: <4787164F.9030805@zytor.com>

H. Peter Anvin wrote:
> 
> Right now, glibc is special-cased.  glibc also tends to be very 
> deliberate about its kernel header inclusions.  It wants a subset of the 
> available defines, so it can include a subset header.
> 
> The reverse is definitely possible too -- all other users (kernel, 
> newlib, dietlibc, uclibc, and klibc) can change and leave the current 
> state for glibc.
> 
> We can special-case the kernel in the above case, but that would involve 
> some additional ugliness.
> 

Just to clarify: I don't have any strong opinions for any particular 
option -- I'm fine with either.  I'd just like to get rid of the 
ugliness of having #defines for any particular user spaces, and I'd 
prefer two include files over feature test macros.

	-hpa

  reply	other threads:[~2008-01-11  7:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200801012029.21432.vapier@gentoo.org>
     [not found] ` <477AF86E.1080309@zytor.com>
     [not found]   ` <200801020830.43449.vapier@gentoo.org>
2008-01-02 18:09     ` [klibc] [patch] import socket defines H. Peter Anvin
2008-01-11  6:16       ` David Miller
2008-01-11  6:23         ` Mike Frysinger
2008-01-11  6:41           ` H. Peter Anvin
2008-01-11  6:47           ` David Miller
2008-01-11  7:02             ` H. Peter Anvin
2008-01-11  7:07             ` Mike Frysinger
2008-01-11  7:10               ` H. Peter Anvin
2008-01-11  7:42                 ` H. Peter Anvin [this message]
2008-01-11  7:57                 ` Mike Frysinger
2008-01-11  8:00                   ` H. Peter Anvin
2008-01-11  9:02                     ` Mike Frysinger
2008-01-11  9:28                       ` Mike Frysinger

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=47871DE4.40906@zytor.com \
    --to=hpa@zytor.com \
    --cc=davem@davemloft.net \
    --cc=klibc@zytor.com \
    --cc=netdev@vger.kernel.org \
    --cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.