public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] fat/msdos/vfat crud removal
Date: 9 Jun 2002 11:49:47 -0700	[thread overview]
Message-ID: <ae080b$6bk$1@cesium.transmeta.com> (raw)
In-Reply-To: <87r8jhc685.fsf@devron.myhome.or.jp> <200206090709.g5979iK439624@saturn.cs.uml.edu> <20020609114638.J13140@suse.de> <m18z5owd9f.fsf@frodo.biederman.org>

Followup to:  <m18z5owd9f.fsf@frodo.biederman.org>
By author:    ebiederm@xmission.com (Eric W. Biederman)
In newsgroup: linux.dev.kernel
>
> Dave Jones <davej@suse.de> writes:
> 
> > On Sun, Jun 09, 2002 at 03:09:44AM -0400, Albert D. Cahalan wrote:
> > 
> >  > There has been talk of removing __KERNEL__ usage from
> >  > some of the header files.
> > 
> > Where? If anything we need to increase __KERNEL__ usage in headers.
> > We export far too much crap which makes no sense to userspace.
> 
> So we should just remove __KERNEL__ altogether.  And say with 2.5.x
> nothing is exported.  Which pretty much has been the official policy
> since user space started using glibc.
> 
> #include <linux/*>
> and 
> #include <asm/*>
> are no longer supported.
> 

In theory, perhaps.  There is plenty that just really can't be done
that way, especially stuff which deals with ioctls and their
structures.

It makes more sense to constrain what is exported to a minimum, but
actually have it be usable.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-06-09 18:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  2:47 [patch] fat/msdos/vfat crud removal Albert D. Cahalan
2002-06-09  4:24 ` OGAWA Hirofumi
2002-06-09  4:32 ` OGAWA Hirofumi
2002-06-09  4:46   ` Albert D. Cahalan
2002-06-09  5:07     ` OGAWA Hirofumi
2002-06-09  6:03       ` Albert D. Cahalan
2002-06-09  6:32         ` OGAWA Hirofumi
2002-06-09  7:09           ` Albert D. Cahalan
2002-06-09  7:49             ` OGAWA Hirofumi
2002-06-09  9:46             ` Dave Jones
2002-06-09 17:52               ` Eric W. Biederman
2002-06-09 18:49                 ` H. Peter Anvin [this message]
2002-06-09 19:00                 ` Thunder from the hill
2002-06-09 19:29                   ` David Woodhouse
2002-06-09 20:19                     ` Thunder from the hill
2002-06-10 13:51                       ` Eric W. Biederman
2002-06-09 21:04                   ` Albert D. Cahalan
2002-06-10 13:55                     ` Eric W. Biederman
2002-06-11 16:49                       ` Jamie Lokier
2002-06-12  6:50                         ` Eric W. Biederman
2002-06-12 11:47                           ` Thunder from the hill
2002-06-09  9:00         ` OGAWA Hirofumi
2002-06-09 13:51         ` Martin Dalecki

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='ae080b$6bk$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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