public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andreas Gruenbacher <a.gruenbacher@computer.org>,
	Nathan Scott <nathans@sgi.com>, Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org, James Morris <jmorris@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: include/linux/xattr.h: how much userpace visible?
Date: Mon, 26 Feb 2007 15:29:58 -0800	[thread overview]
Message-ID: <45E36D76.5030507@zytor.com> (raw)
In-Reply-To: <20060724184534.GA26842@mars.ravnborg.org>

Sam Ravnborg wrote:
> The userspace headers are supposed to hold the part of the kernel
> definitions that glibc (and mayby the attr package) uses. If they happen
> to have their own copy now should not impct the decision what is part of
> the userspace interface for the kernel. So actual usage does not decide
> what is part of the userspace kernel headers but what definitionas are
> definitions the userspace <-> kernel interface.

glibc, or another libc.

Basically, the kernel should be able to export the things that userspace 
needs to be able to correctly speak the ABI.

	-hpa

  parent reply	other threads:[~2007-02-26 23:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23 18:43 include/linux/xattr.h: how much userpace visible? Adrian Bunk
2006-07-23 19:26 ` Alexey Dobriyan
2006-07-23 22:57 ` Nathan Scott
2006-07-24 18:31   ` Andreas Gruenbacher
2006-07-24 18:45     ` Sam Ravnborg
2006-07-24 18:58       ` Andreas Gruenbacher
2007-02-26 23:29       ` H. Peter Anvin [this message]
2007-02-26 23:28     ` H. Peter Anvin
2007-02-26 23:43       ` David Miller
2007-02-26 23:52         ` H. Peter Anvin
2007-02-27  0:03           ` Christoph Hellwig
2007-02-27  0:10             ` H. Peter Anvin
2007-02-27  1:49               ` Kyle Moffett
2007-02-27  2:09                 ` H. Peter Anvin

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=45E36D76.5030507@zytor.com \
    --to=hpa@zytor.com \
    --cc=a.gruenbacher@computer.org \
    --cc=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=sam@ravnborg.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