All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: [RFC] driver core support for i2c bus and drivers
Date: Thu, 19 May 2005 06:23:50 +0000	[thread overview]
Message-ID: <3E767D17.5030607@paradyne.com> (raw)
In-Reply-To: <20030310072337.GJ6512@kroah.com>

Sounds good. Thanks for volunteering to do the userspace changes.
I can also do them. I maintain most of them in our package.
(not that the changes are likely to be hard - look for a file
in one place, if it isn't there, look in the next place...)
Of course there are programs outside of our package that
access our /proc info directly or indirectly through
our libsensors library, they would get broken too.

The oops problem is present in CVS but not in our 2.7.0 release, correct?

Greg KH wrote:
> On Mon, Mar 17, 2003 at 08:31:35PM -0500, Mark D. Studebaker  wrote:
> 
>>our userspace tools use the /proc/bus/i2c file and (of course) the entire
>>tree of exported sysctl info under /proc/sys/dev/sensors
>>(as implemented in i2c-proc.c).
> 
> 
> Right now, the /proc and sysctl code is not changed at all.
> 
> However, the end goal will be to remove the /proc and sysctl code
> entirely, and just use sysfs, as this is exactly what sysfs is for.  I
> know, in order to do this properly the userspace library will need to be
> changed, and I'm willing to do this work too.  I do not want to break
> userspace compatibility needlessly.
> 
> I'll not remove anything until the same functionality can be achieved,
> is this ok?  I will, of course, provide patches that for people to
> evaluate, when it's working...
> 
> 
>>Does your proposal or Cristoph's recent changes affect these?
> 
> 
> Christoph's changes preserve the existing code, but make it work without
> oopses :)
> 
> thanks,
> 
> greg k-h

  parent reply	other threads:[~2005-05-19  6:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10  7:23 [RFC] driver core support for i2c bus and drivers Greg KH
2005-05-19  6:23 ` Greg KH
2003-03-10 22:09 ` Albert Cranford
2005-05-19  6:23   ` Albert Cranford
2003-03-10 22:12   ` Greg KH
2005-05-19  6:23     ` Greg KH
2005-05-19  6:23 ` Mark D. Studebaker  [this message]
2005-05-19  6:23 ` Greg KH
2005-05-19  6:23 ` Mark D. Studebaker 
2003-03-18  1:27   ` Greg KH
2005-05-19  6:23     ` 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=3E767D17.5030607@paradyne.com \
    --to=mds@paradyne.com \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.