public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kaiwan N Billimoria <kaiwan@designergraphix.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stuck creating sysfs hooks for a driver..
Date: Wed, 15 Feb 2006 14:13:01 -0800	[thread overview]
Message-ID: <20060215221301.GA25941@kroah.com> (raw)
In-Reply-To: <43F2DE34.60101@designergraphix.com>

On Wed, Feb 15, 2006 at 01:24:28PM +0530, Kaiwan N Billimoria wrote:
> Hello All,
> 
> I am in the process of porting a 2.4 temperature sensor device driver (the 
> National Semiconductor LM70CILD-3 temperature sensor eval board) to the 2.6 
> Linux kernel (specifically to v 2.6.15.3 <http://2.6.15.3>), with the 
> intention of submitting it for inclusion. All ok, except this: am stuck on 
> inserting an entry in /sys instead of /proc for the
> driver (as that is suggested as the new "correct" interface to userspace).

Have you read Documentation/hwmon/sysfs-interface?  I think that,
combined with using the hwmon class code is what you want to use here.

Hope this helps,

greg k-h

  reply	other threads:[~2006-02-15 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15  7:54 Stuck creating sysfs hooks for a driver Kaiwan N Billimoria
2006-02-15 22:13 ` Greg KH [this message]
2006-02-16 11:33   ` Kaiwan N Billimoria
2006-02-16 12:16     ` Arjan van de Ven
2006-02-16 16:41     ` Greg KH
2006-02-19 13:23     ` Jean Delvare
2006-02-21  6:18       ` Kaiwan N Billimoria
2006-03-31  6:01       ` SPI <-> Parport (light) bridge code (Re: Stuck creating sysfs hooks for a driver..) Kaiwan N Billimoria
     [not found] <pan.2006.02.15.08.46.27.708727@bfh.ch>
2006-02-15  8:48 ` Stuck creating sysfs hooks for a driver Seewer Philippe

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=20060215221301.GA25941@kroah.com \
    --to=greg@kroah.com \
    --cc=kaiwan@designergraphix.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox