From: Joe Korty <joe.korty@ccur.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jeff Garzik <jeff@garzik.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.16
Date: Mon, 20 Mar 2006 14:32:20 -0500 [thread overview]
Message-ID: <20060320193220.GA18472@tsunami.ccur.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603202022590.3457@yvahk01.tjqt.qr>
On Mon, Mar 20, 2006 at 08:25:21PM +0100, Jan Engelhardt wrote:
> >
> > strace should be using sanitized versions of the kernel headers, not directly
> > including them verbatim...
> >
> Now, would not it be good for everyone if the in-kernel headers get
> every bit of sanitation? Especially those who are stuck with outdated
> versions of sanitized headers (thinking of FC3 and FC4) often do the
> magic symlinking (/usr/include/linux -> /usr/src/linux/include/linux).
Also, if the policy is that only kernel code can reference the kernel
headers, this intent should be more strongly enforced by removing all
occurances of #ifdef __KERNEL__ in said headers.
Joe
next prev parent reply other threads:[~2006-03-20 19:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 6:23 Linux v2.6.16 Linus Torvalds
2006-03-20 12:02 ` 2.6.16.x will be a long-living kernel series Adrian Bunk
2006-03-20 12:05 ` Arjan van de Ven
2006-03-20 12:12 ` Adrian Bunk
2006-03-20 13:03 ` Arjan van de Ven
2006-03-24 0:22 ` Adrian Bunk
2006-03-20 19:22 ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04 ` Jeff Garzik
2006-03-20 19:25 ` Jan Engelhardt
2006-03-20 19:32 ` Joe Korty [this message]
2006-03-20 19:33 ` Linus Torvalds
2006-03-20 21:05 ` Andreas Schwab
2006-03-20 22:52 ` Matthias Andree
2006-03-22 5:22 ` Peter Williams
2006-03-22 6:31 ` Ashok Raj
2006-03-22 13:08 ` Ashok Raj
2006-03-22 13:25 ` Michal Piotrowski
2006-03-22 17:39 ` Rafael J. Wysocki
2006-03-22 17:54 ` Ashok Raj
2006-03-22 18:11 ` Rafael J. Wysocki
2006-03-22 18:27 ` Ashok Raj
2006-03-22 20:40 ` Rafael J. Wysocki
2006-03-22 21:00 ` Ashok Raj
2006-03-22 21:36 ` Rafael J. Wysocki
2006-03-22 22:27 ` Peter Williams
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09 ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01 9:18 ` netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error Adrian Bunk
[not found] <5Sm46-2a7-13@gated-at.bofh.it>
[not found] ` <5T455-7j-11@gated-at.bofh.it>
[not found] ` <5T5aR-1DN-23@gated-at.bofh.it>
[not found] ` <5Tbgl-2dp-43@gated-at.bofh.it>
2006-03-23 0:05 ` Linux v2.6.16 Bodo Eggert
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=20060320193220.GA18472@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=jeff@garzik.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.