From: Richard Purdie <rpurdie@openedhand.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, "kay.sievers" <kay.sievers@vrfy.org>
Cc: "Bryn M. Reeves" <breeves@redhat.com>,
John Lenz <lenz@cs.wisc.edu>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [patch] Move led attributes out of device name and into sysfs attributes, was Re: LED devices
Date: Fri, 01 Jun 2007 16:43:12 +0100 [thread overview]
Message-ID: <1180712592.6390.139.camel@localhost.localdomain> (raw)
In-Reply-To: <1180710270.3782.5.camel@localhost.localdomain>
On Fri, 2007-06-01 at 16:04 +0100, Richard Hughes wrote:
> Patch attached corrects all the brokenness with the led class (encoding
> some attributes in the device handle).
For the benefit of LKML, there has been some discussion of this
elsewhere. My arguments do not particularly come across in Richard's
choice of quoting and I'm a little annoyed he's chosen to do things this
way, particularly before any further feedback from Greg/Kay but so be
it.
Greg said that the LEDs class should export any property data as a class
attribute rather than this just being available in the device name. I
added the patch in
http://git.o-hand.com/?p=linux-rpurdie-leds;a=shortlog;h=for-mm to deal
with this, without breaking the existing LED naming and documented API.
Greg said that the only requirement on bus id naming was that it needed
to be unique so this should therefore be compatible. HAL could then go
ahead and ignore the device name, all the attributes are there in the
fashion it needs which was the original complaint.
I accept this is basically out of my hands now. Greg/Kay have the
appropriate emails and if they'll let me know which approach they want
to take, I'll apply an appropriate patch. I'd suggest not applying this
patch directly as it introduces a race in the error path it alters.
Richard
next prev parent reply other threads:[~2007-06-01 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 15:04 Richard Hughes
2007-06-01 15:43 ` Richard Purdie [this message]
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
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=1180712592.6390.139.camel@localhost.localdomain \
--to=rpurdie@openedhand.com \
--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 \
/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
all inboxes | Powered by JetHome®