From: "Chris Friesen" <cfriesen@nortel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: using kernel headers in libc headers
Date: Mon, 30 Nov 2009 11:40:22 -0600 [thread overview]
Message-ID: <4B140386.8030702@nortel.com> (raw)
In-Reply-To: <4B13FA4E.1070901@zytor.com>
On 11/30/2009 11:01 AM, H. Peter Anvin wrote:
> A better way is to factor out subsets; if <linux/sched.h> has too many
> things, we can break out the POSIX parts into <linux/sched_posix.h> or
> (certainly better if we have more than one of these)
> <linux/sched/posix.h> which can also be included by <linux/sched.h>.
>
> glibc can then choose to include or not include <linux/sched/posix.h>
> depending on its configuration. The configuration macros remain a glibc
> internal detail.
Yes, absolutely. Personally I find it much easier to open a separate
header file than to read code that is littered with #ifdefs.
Chris
next prev parent reply other threads:[~2009-11-30 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 16:37 using kernel headers in libc headers Ulrich Drepper
2009-11-30 17:01 ` H. Peter Anvin
2009-11-30 17:40 ` Chris Friesen [this message]
2009-11-30 17:43 ` Ulrich Drepper
2009-11-30 17:55 ` H. Peter Anvin
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=4B140386.8030702@nortel.com \
--to=cfriesen@nortel.com \
--cc=drepper@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.