From: Greg KH <greg@kroah.com>
To: Johannes Stezenbach <js@convergence.de>,
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 11:01:05 -0800 [thread overview]
Message-ID: <20031212190105.GB3038@kroah.com> (raw)
In-Reply-To: <20031212185357.GB32169@convergence.de>
On Fri, Dec 12, 2003 at 07:53:57PM +0100, Johannes Stezenbach wrote:
> On Fri, Dec 12, 2003 at 09:56:57AM -0800, Greg KH wrote:
> > On Fri, Dec 12, 2003 at 03:56:52PM +0100, Johannes Stezenbach wrote:
> > >
> > > I had some trouble compiling a userspace application
> > > which uses the I2C device interface (the DirectFB
> > > Matrox driver). Apparently some stuff has been removed
> > > from i2c-dev.h
> >
> > Yes it has. Do not use the kernel headers in your userspace
> > application. If you need this interface, use the updated i2c-dev.h that
> > is in the lmsensors release. That is the proper file.
>
> 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.
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.
So please use the headers that are present in the lmsensors project, or
copy those headers into your project.
I don't want this thread to drag out into the usual argument for or
against this issue, please.
> 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.
greg k-h
next prev parent reply other threads:[~2003-12-12 19:02 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 [this message]
2003-12-12 19:21 ` Johannes Stezenbach
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=20031212190105.GB3038@kroah.com \
--to=greg@kroah.com \
--cc=js@convergence.de \
--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