From: Greg KH <greg@kroah.com>
To: Valdis.Kletnieks@vt.edu
Cc: Pavel Machek <pavel@ucw.cz>, Zhang Rui <rui.zhang@intel.com>,
linux-acpi <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Richard Purdie <rpurdie@rpsys.net>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices
Date: Tue, 4 Aug 2009 10:36:27 -0700 [thread overview]
Message-ID: <20090804173627.GA23848@kroah.com> (raw)
In-Reply-To: <19631.1249406664@turing-police.cc.vt.edu>
On Tue, Aug 04, 2009 at 01:24:24PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 04 Aug 2009 08:10:42 PDT, Greg KH said:
> > On Tue, Aug 04, 2009 at 03:21:29PM +0200, Pavel Machek wrote:
> > > On Mon 2009-08-03 17:10:57, Zhang Rui wrote:
>
> > > > cat /sys/class/als/als0/mappings
> > > > ???Illuminance Adjustment
> > > > 0 70
> > > > 10 73
> > > > 80 85
> > > > 300 100
> > > > 1000 150
> > >
> > > There's one value per file for sysfs... You should definitely have the
> > > header.
> >
> > No, no "header", just don't do this, it's not allowed. Again,
> > one-value-per-sysfs-file is the rule, please do not violate it.
>
> What's the intended sysfs solution here, then? Make 'mappings' a directory,
> and populate it with files called 0, 10, 80, 300, 1000, each with one number
> in them?
That's one acceptable solution. Or how about files in this directory
called "mapping_0", "mapping_10", and so on, containing the adjustment
value?
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-04 17:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 9:10 [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices Zhang Rui
2009-08-04 1:12 ` ykzhao
2009-08-04 1:12 ` ykzhao
2009-08-04 7:30 ` Zhang Rui
2009-08-04 13:21 ` Pavel Machek
2009-08-04 15:10 ` Greg KH
2009-08-04 17:24 ` Valdis.Kletnieks
2009-08-04 17:36 ` Greg KH [this message]
2009-08-05 1:04 ` Zhang Rui
2009-08-05 16:10 ` Valdis.Kletnieks
2009-08-06 1:51 ` Zhang Rui
2009-08-05 0:55 ` Zhang Rui
2009-08-05 0:55 ` Zhang Rui
2009-08-05 1:02 ` Zhang Rui
2009-08-05 16:19 ` Pavel Machek
2009-08-06 1:41 ` Zhang Rui
2009-08-06 7:13 ` Pavel Machek
2009-08-06 8:47 ` Zhang Rui
2009-08-06 9:52 ` Pavel Machek
2009-08-17 8:32 ` Zhang Rui
2009-08-21 11:51 ` Pavel Machek
2009-08-25 1:13 ` Zhang Rui
2009-08-25 1:13 ` Zhang Rui
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=20090804173627.GA23848@kroah.com \
--to=greg@kroah.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=rui.zhang@intel.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 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.