From: Christoph Hellwig <hch@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, zach@vmware.com, linux-kernel@vger.kernel.org,
hch@infradead.org, linuxppc-dev@ozlabs.org, galak@freescale.com,
davem@davemloft.net
Subject: Re: [PATCH] ppc32: removed usage of <asm/segment.h>
Date: Wed, 17 Aug 2005 10:09:20 +0100 [thread overview]
Message-ID: <20050817090920.GA12716@infradead.org> (raw)
In-Reply-To: <E1E5Jii-0004Yc-00@dorka.pomaz.szeredi.hu>
On Wed, Aug 17, 2005 at 10:56:24AM +0200, Miklos Szeredi wrote:
> > On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> > > >I concur, in fact we should really kill that thing off entirely.
> > >
> > > I'm all for killing it off entirely but got some feedback that on
> > > i386 segment.h can be included by userspace programs.
> >
> > No kernel headers can be included by userland anymore.
>
> I know nothing about <asm/segment.h> but this generic statement is
> simply not true.
>
> There are perfectly valid uses of kernel headers from userspace. For
> example if a program uses the netlink interface, it should include
> <linux/netlink.h>. It's the interface definition after all.
>
> Glibc headers also include <linux/*> and <asm/*> in quite few places.
But these files in /usr/include/ aren't provided by the kernel anymore.
next prev parent reply other threads:[~2005-08-17 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:00 [PATCH] ppc32: removed usage of <asm/segment.h> Kumar Gala
2005-08-17 1:38 ` Paul Mackerras
2005-08-17 3:33 ` David S. Miller
2005-08-17 5:43 ` Kumar Gala
2005-08-17 8:16 ` Geert Uytterhoeven
2005-08-17 8:30 ` Christoph Hellwig
2005-08-17 8:56 ` Miklos Szeredi
2005-08-17 9:09 ` Christoph Hellwig [this message]
2005-08-17 9:15 ` Miklos Szeredi
2005-08-17 9:20 ` Christoph Hellwig
2005-08-17 10:07 ` Miklos Szeredi
2005-08-18 16:25 ` Kumar Gala
2005-08-18 23:40 ` Paul Mackerras
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=20050817090920.GA12716@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=galak@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miklos@szeredi.hu \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).