From: Richard Hughes <hughsient@gmail.com>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: Greg KH <greg@kroah.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: Tue, 26 Jun 2007 11:46:38 +0100 [thread overview]
Message-ID: <1182854798.16516.5.camel@work> (raw)
In-Reply-To: <1182852173.11449.22.camel@localhost.localdomain>
On Tue, 2007-06-26 at 11:02 +0100, Richard Purdie wrote:
> There were some other opinions voiced including one from the person
> who started this discussion.
>
> So no, the people who write the tools that parse sysfs (like HAL.)
> don't appreciate this.
>
> People who write tools that parse sysfs like shell scripts don't
> appreciate it either, as I illustrated.
>From a hal point of view, we don't care if the device name is 'led01' or
'light_to_dance_the_fandango' and from a shell point of view it's
probably best for the latter. I think the point Greg tried to make is
that it shouldn't matter, and HAL shouldn't export (nor parse) the
device name as anything sensible.
> You've yet to give any technical reason why we can't have meaningful
> busids rather than random numbers. Your entire argument seems to be
> that its wrong because its a bit different and nobody else does it...
If it's a trivial name then I think led_thinklight0 is perfectly okay, I
think Kay was talking more about the attribute vs. name-in-device
encoding.
Richard.
next prev parent reply other threads:[~2007-06-26 10:47 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 [this message]
2007-06-28 19:15 ` Kay Sievers
2007-06-10 10:11 ` Pavel Machek
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=1182854798.16516.5.camel@work \
--to=hughsient@gmail.com \
--cc=breeves@redhat.com \
--cc=greg@kroah.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