From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
Cc: Richard Purdie <rpurdie@openedhand.com>,
Richard Hughes <hughsient@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"kay.sievers" <kay.sievers@vrfy.org>,
"Bryn M. Reeves" <breeves@redhat.com>,
John Lenz <lenz@cs.wisc.edu>
Subject: Re: [patch] Move led attributes out of device name and into sysfs attributes, was Re: LED devices
Date: Sun, 10 Jun 2007 12:11:55 +0200 [thread overview]
Message-ID: <20070610101155.GA25070@elf.ucw.cz> (raw)
In-Reply-To: <20070608185710.GB14372@kroah.com>
Hi!
> > My other concerns with this patch are that it exports incorrect
> > information on spitz (which I had warned about and I will get bug
> > reports about) and that "description" is not really a suitable name for
> > a sysfs attribute, "function" might give a better idea of what it
> > represents to developers.
> >
> > I still question whether either colour or function properties are
> > actually particularly useful to userspace other than for naming purposes
> > which is why they were part of the device name.
> >
> > Anyhow, I'm trying not to say too much more as it will just go in
> > circles. I'll await a reply from Greg.
>
> Hm, I thought I made my opinion pretty clear in the beginning.
>
> Why not just do a simple:
> led01
> led02
> led03
> ...
>
> and so on?
>
> And use the 'name' field to put the name of your device (disk,
> bluetooth, etc.) This is the way all other busses and devices work, and
> I don't think that LEDs are anything more "special" than anything else
> in the kernel, right?
Can we keep the original naming? spitz:disk is as unique as led02, and
it is _way_ easier to use.
Come on, I want to use the led subsystem from the scripts...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-06-10 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 15:04 [patch] Move led attributes out of device name and into sysfs attributes, was Re: LED devices Richard Hughes
2007-06-01 15:43 ` Richard Purdie
2007-06-01 15:59 ` Richard Hughes
2007-06-01 16:23 ` Richard Purdie
2007-06-08 18:57 ` Greg KH
2007-06-08 23:02 ` Richard Purdie
2007-06-08 23:46 ` Greg KH
2007-06-09 9:25 ` Richard Purdie
2007-06-25 5:06 ` Greg KH
2007-06-26 10:02 ` Richard Purdie
2007-06-26 10:46 ` Richard Hughes
2007-06-28 19:15 ` Kay Sievers
2007-06-10 10:11 ` Pavel Machek [this message]
2007-06-10 20:02 ` Richard Hughes
2007-06-11 1:57 ` Henrique de Moraes Holschuh
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=20070610101155.GA25070@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=breeves@redhat.com \
--cc=greg@kroah.com \
--cc=hughsient@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@openedhand.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