From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org, chaffee@cs.berkeley.edu
Subject: Re: [patch] fat/msdos/vfat crud removal
Date: Sun, 09 Jun 2002 16:49:54 +0900 [thread overview]
Message-ID: <87fzzwdh7h.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200206090709.g5979iK439624@saturn.cs.uml.edu>
"Albert D. Cahalan" <acahalan@cs.uml.edu> writes:
> Long ago, it was considered OK to use the kernel headers
> in app code. This is the case with Linux 2.0 and libc 5.
> (it used to be OK to symlink /usr/include/linux into an
> unmodified copy of the Linux kernel source)
>
> There has been a weak effort to avoid breaking libc 5.
>
> Using __KERNEL__ might make it easier to provide cleaned
> headers for user code.
>
> There has been talk of removing __KERNEL__ usage from
> some of the header files.
So, are you going to remove __KERNEL__ stuff, although the program for
linux uses it? And are you going to fix program using it?
I don't want to do.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2002-06-09 7: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 [this message]
2002-06-09 9:46 ` Dave Jones
2002-06-09 17:52 ` Eric W. Biederman
2002-06-09 18:49 ` H. Peter Anvin
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=87fzzwdh7h.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=acahalan@cs.uml.edu \
--cc=chaffee@cs.berkeley.edu \
--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 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.