From: Albert Cranford <ac9410@attbi.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] More i2c driver changes for 2.5.66
Date: Thu, 03 Apr 2003 01:21:13 -0500 [thread overview]
Message-ID: <3E8BD2D9.8050002@attbi.com> (raw)
In-Reply-To: 1049328958830@kroah.com
I read the thread concerning the removal of proc.c & proc.h
but hope that this does not go to Linus until the interface
between i2c & sensors to application is somewhat defined.
At the moment we have a sysctl API used by sensors, video and
other i2c kernel applications that is working.
Our desire to switch the sensors to sysfs interface should not
break other applications. At least until we have a model/api
to propose to these other drivers.
In my personal home systems I use it87 driver and have been
somewhat successful in switching to sysfs. A big blocking
point is there is no application to read/set/monitor the
driver, so it is basically unverified. I would hate to
put other i2c applications in the same boat.
Your thoughts?
Albert
Greg KH wrote:
> ChangeSet 1.977.29.8, 2003/04/02 11:45:21-08:00, greg@kroah.com
>
> i2c: remove proc and sysctl code from i2c-proc as it is no longer used.
>
next prev parent reply other threads:[~2003-04-03 6:09 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 [this message]
2003-04-03 6:33 ` Greg KH
2003-04-03 13:06 ` Albert Cranford
2003-04-03 16:37 ` Greg KH
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=3E8BD2D9.8050002@attbi.com \
--to=ac9410@attbi.com \
--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