From: Richard Purdie <rpurdie@rpsys.net>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Justin Mattock <justinmattock@gmail.com>,
Julien BLACHE <jb@jblache.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.25 intended change: smc:kbd_backlight vs. smc::kbd_backlight ?
Date: Sat, 05 Apr 2008 17:22:33 +0100 [thread overview]
Message-ID: <1207412553.5021.46.camel@dax.rpnet.com> (raw)
In-Reply-To: <1207409620.4224.10.camel@localhost>
On Sat, 2008-04-05 at 17:33 +0200, Soeren Sonnenburg wrote:
> On Sat, 2008-04-05 at 11:42 +0100, Richard Purdie wrote:
> > Basically the LED names were a mess, there is a documented standard
> > which has been there since the beginning (Documentation/leds-class.txt)
> > and a number of drivers didn't follow that. That standardisation commit
> > was an attempt to deal with this problem once and for all and in that
> > sense its a bugfix, not a regression. The fact function wasn't part of
> > the original naming scheme was a mistake (see previous discussions on
> > LKML) which we're trying to address without breaking the documented
> > standard. The side effect is that some existing drivers need to be
> > updated to match the documentation (and should never have been merged in
> > the first place because of that) :(.
>
> So to make it clear "devicename:colour:function" means in the case of
> applesmc smc::kbd_backlight because there is no colour defined. One
> could have used "devicename:function:colour" without breaking things -
> no ?
No, since devicename:colour was there from the start and the
documentation said we could append to it.
> So it seems we will have to file bug reports to the led dealing
> userspace programs ...
I'm afraid so, not ideal but we need to get this sorted out properly
once and for all.
Regards,
Richard
prev parent reply other threads:[~2008-04-05 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 18:58 Soeren Sonnenburg
2008-04-04 6:54 ` Soeren Sonnenburg
2008-04-04 15:12 ` Justin Mattock
2008-04-05 5:32 ` Soeren Sonnenburg
2008-04-05 6:44 ` Justin Mattock
2008-04-05 6:51 ` Soeren Sonnenburg
2008-04-05 10:42 ` Richard Purdie
2008-04-05 15:33 ` Soeren Sonnenburg
2008-04-05 16:22 ` Richard Purdie [this message]
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=1207412553.5021.46.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=jb@jblache.org \
--cc=justinmattock@gmail.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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®