From: Greg KH <greg@kroah.com>
To: Albert Cranford <ac9410@attbi.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] More i2c driver changes for 2.5.66
Date: Thu, 3 Apr 2003 08:37:57 -0800 [thread overview]
Message-ID: <20030403163757.GA4473@kroah.com> (raw)
In-Reply-To: <3E8C31BE.5060000@attbi.com>
On Thu, Apr 03, 2003 at 08:06:06AM -0500, Albert Cranford wrote:
> Your right, nobody outside of sensors uses i2c-proc, but
> why not create a new i2c-sysfs.h in drivers/i2c locally
> and and adjust the couple of existing drivers.
What would i2c-sysfs.h be needed for? All of the needed sysfs prototype
functions are already in device.h.
> We all know the application library is not going to have
> access to include/linux/include/i2c-xxxx.h anyhow.
It never did :)
> Later we can completely remove linux/include/linux/i2c-proc.h
> which the existing application library relies upon.
No userspace program should rely on kernel header files.
And I didn't take away the functionality that i2c-proc.h provided with
the list of devices supported and such. Just the unused function
prototypes that dealt with the proc and sysctl interface.
thanks,
greg k-h
prev parent reply other threads:[~2003-04-03 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 0:14 [BK PATCH] More i2c driver changes for 2.5.66 Greg KH
2003-04-03 0:15 ` [PATCH] " Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 0:15 ` Greg KH
2003-04-03 6:21 ` Albert Cranford
2003-04-03 6:33 ` Greg KH
2003-04-03 13:06 ` Albert Cranford
2003-04-03 16:37 ` Greg KH [this message]
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=20030403163757.GA4473@kroah.com \
--to=greg@kroah.com \
--cc=ac9410@attbi.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