linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Greg KH <greg@kroah.com>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11: i2c-dev.h for userspace
Date: Fri, 12 Dec 2003 20:21:32 +0100	[thread overview]
Message-ID: <20031212192132.GC32169@convergence.de> (raw)
In-Reply-To: <20031212190105.GB3038@kroah.com>

On Fri, Dec 12, 2003 at 11:01:05AM -0800, Greg KH wrote:
> On Fri, Dec 12, 2003 at 07:53:57PM +0100, Johannes Stezenbach wrote:
> > 
> > I think you create a mess here. Other drivers have usable
> > API include files in /usr/include/linux, why are i2c.h and i2c-dev.h
> > special?
> 
> They aren't.  The rule is:
> 	DO NOT INCLUDE KERNEL HEADER FILES IN USERSPACE TOOLS.
> Please read the archives for lkml on why this is true.

I've read this statement multiple times on lkml, from Linus
and others. And you won't believe it: I'm all for a separation
of driver API includes and kernel includes.

But:

> Yeah, we do need a way to have "sanitized" kernel headers so that
> userspace can include them, but for now, use what your libc provides.

IMHO the problem is that Linux 2.6.0 is about to be released with some
broken driver API include files, and without a clear policy how driver
authors, glibc and distribution maintainers and should handle
the situation in a consistent way.


> > I think that sucks.
> 
> Sorry you feel that way, but the i2c header is not going to be any
> different than any other kernel header at this time.

I think they are different now.


Johannes

  reply	other threads:[~2003-12-12 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 14:56 2.6.0-test11: i2c-dev.h for userspace Johannes Stezenbach
2003-12-12 17:56 ` Greg KH
2003-12-12 18:53   ` Johannes Stezenbach
2003-12-12 19:01     ` Greg KH
2003-12-12 19:21       ` Johannes Stezenbach [this message]
2003-12-12 19:45         ` Greg KH
2003-12-14  1:57       ` bill davidsen

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=20031212192132.GC32169@convergence.de \
    --to=js@convergence.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.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).