public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
Cc: Michael Holzheu <HOLZHEU@de.ibm.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Ingo Oeser <ioe-lkml@rameria.de>,
	linux-kernel@vger.kernel.org, mschwid2@de.ibm.com
Subject: Re: How to document dimension units for virtual files?
Date: Mon, 13 Nov 2006 13:18:02 +0100	[thread overview]
Message-ID: <20061113121802.GC31613@elf.ucw.cz> (raw)
In-Reply-To: <20061110065336.GA13646@kroah.com>

Hi!

> > If you want to export data to userspace via a virtual filesystem
> > like sysfs, the following rules are recommended:
> 
> Um, does this mean you expect us to change all of the currently existing
> sysfs file names?  And people get mad at me when I just move sysfs
> symlinks around...
> 
> Look at the hwmon drivers, and the documentation in
> Documentation/hwmon/sysfs-interface for a description of how we have
> been documenting this already.
> 
> In short, I don't really think we need to encode the units in the file
> name, somehow we have done pretty well without it so far :)

Well, problem is that some notebooks have battery capacity in mAh, and
some in mWh, and you can't convert between those.

We could do something like 

battery_stored_energy and battery_stored_current
                 (mWh)                      (mAh)

...but it looks ugly, and battery_capacity:mAh does not sound that bad
for a new interface.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2006-11-13 12:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:54 How to document dimension units for virtual files? Michael Holzheu
2006-11-08 17:04 ` Randy Dunlap
2006-11-08 18:27   ` Michael Holzheu
2006-11-10  6:53     ` Greg KH
2006-11-10 10:03       ` Michael Holzheu
2006-11-13 17:16         ` Greg KH
2006-11-13 12:18       ` Pavel Machek [this message]
2006-11-13 17:46         ` Henrique de Moraes Holschuh
2006-11-14  8:50           ` Michael Holzheu
2006-11-08 17:09 ` Jörn Engel
2006-11-08 18:32   ` Michael Holzheu
2006-11-08 18:01 ` Henrique de Moraes Holschuh
2006-11-08 18:37   ` Michael Holzheu
2006-11-08 19:59     ` Henrique de Moraes Holschuh
2006-11-09 23:15 ` Pavel Machek
2006-11-10 13:18   ` Kyle Moffett
2006-11-10 15:41     ` Sanjoy Mahajan
2006-11-13  4:33       ` Kyle Moffett
  -- strict thread matches above, loose matches on Subject: below --
2006-10-23 12:32 Michael Holzheu
2006-10-23 19:03 ` Ingo Oeser
2006-10-24 14:15   ` Michael Holzheu
2006-10-24 20:13     ` Arnd Bergmann
2006-10-28 18:40     ` Pavel Machek

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=20061113121802.GC31613@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=HOLZHEU@de.ibm.com \
    --cc=greg@kroah.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschwid2@de.ibm.com \
    --cc=randy.dunlap@oracle.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