[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090923071857.GC8565@elf.ucw.cz>
Date: Wed, 23 Sep 2009 09:18:57 +0200
From: Pavel Machek <pavel@....cz>
To: Jonathan Cameron <jic23@....ac.uk>
Cc: Zhang Rui <rui.zhang@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-acpi <linux-acpi@...r.kernel.org>,
Jean Delvare <khali@...ux-fr.org>,
"alan@...ux.intel.com" <alan@...ux.intel.com>,
Len Brown <lenb@...nel.org>,
"Cory T. Tusar" <ctusar@...eon-central.com>,
"Trisal, Kalhan" <kalhan.trisal@...el.com>
Subject: Re: [RFC] [PATCH 1/2] introduce ALS sysfs class
On Tue 2009-09-22 13:42:23, Jonathan Cameron wrote:
> Zhang Rui wrote:
> > Hi, Jonathan,
> >
> > this is the refresh ALS sysfs class driver.
> > I just introduced one sysfs attribute "illuminance", because
> > I didn't catch the exact meaning of the others like "???infrared".
> > So it would be great if you can generate an incremental patch
> > to introduce the other optional attributes needed, and update
> > the documentation as well. :)
> Will do, though may just leave it out of first pass of drivers
> (as it may be controversial and it would be nice to get something
> in place before the arguments begin!)
>
> All looks nice and clean. The only real question is whether
> we want to standardize naming of devices under sysfs (like hwmon does)
> or allow the individual drivers to do the naming?
Allow the drivers to do the naming. Having useless name like "als0",
with als0/name telling me what the driver is is bad.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists