From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dave Jones <davej@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.5.2.7: io.h cleanup and userspace nudge
Date: Fri, 04 Jan 2002 13:12:03 -0500 [thread overview]
Message-ID: <3C35F073.54E89624@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201041858400.20620-100000@Appserv.suse.de>
Dave Jones wrote:
>
> On Fri, 4 Jan 2002, Jeff Garzik wrote:
>
> > As we are now in 2.5.x series I figured it might be a good time to push
> > this out... The patch removes __KERNEL__ ifdefs from [only] io.h as a
> > nudge to userspace that they should not be including kernel headers.
>
> Why not..
>
> #ifndef __KERNEL__
> #error This file should not be included by userspace.
> #endif
I thought about it, but then the tree would be littered with that all
over the place. Programmers are smart enough to figure this out (I hope
:))
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2002-01-04 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 17:47 PATCH 2.5.2.7: io.h cleanup and userspace nudge Jeff Garzik
2002-01-04 18:00 ` Dave Jones
2002-01-04 18:12 ` Jeff Garzik [this message]
2002-01-04 18:18 ` Dave Jones
2002-01-04 18:20 ` David Woodhouse
2002-01-04 18:39 ` Alan Cox
2002-01-04 18:46 ` including kernel headers (was Re: PATCH 2.5.2.7: io.h cleanup and userspace nudge) Jeff Garzik
2002-01-04 18:21 ` PATCH 2.5.2.7: io.h cleanup and userspace nudge Jeff Garzik
2002-01-04 18:24 ` Dave Jones
2002-01-04 18:31 ` Richard Gooch
2002-01-04 18:35 ` Jeff Garzik
2002-01-04 18:40 ` Dave Jones
2002-01-04 18:41 ` Richard Gooch
2002-01-04 19:16 ` Mike Castle
2002-01-04 23:28 ` Reid Hekman
2002-01-04 18:19 ` Oliver Xymoron
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=3C35F073.54E89624@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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