linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: rpurdie@rpsys.net
Cc: Julien BLACHE <jb@jblache.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25 intended change: smc:kbd_backlight vs. smc::kbd_backlight ?
Date: Fri, 04 Apr 2008 08:54:28 +0200	[thread overview]
Message-ID: <1207292068.4511.10.camel@localhost> (raw)
In-Reply-To: <1207162690.9669.11.camel@localhost>

On Wed, 2008-04-02 at 20:58 +0200, Soeren Sonnenburg wrote:
> Dear all,
> 
> I am wondering whether the change from 
> 
> /sys/devices/platform/applesmc.768/leds/smc:kbd_backlight  (2.6.24) 
> /sys/devices/platform/applesmc.768/leds/smc::kbd_backlight (2.6.25)
> 
> is intentional?
> 
> I recognized that it breaks current userspace applications changing the
> keyboard background leds like pommed...

OK it looks like commit 6c152beefbf90579d21afc4f7e075b1f801f9a75 from
Richard Purdie, 'leds: Standardise LED naming scheme' introduced this
change.

Why do we need '::' instead of a single ':' (that would not have broken
things)?

Also sometimes only a single ':' seperator is used like in
corgi:green:mail but e.g. not in clevo::mail ?!

Soeren

  reply	other threads:[~2008-04-04  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 18:58 2.6.25 intended change: smc:kbd_backlight vs. smc::kbd_backlight ? Soeren Sonnenburg
2008-04-04  6:54 ` Soeren Sonnenburg [this message]
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

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=1207292068.4511.10.camel@localhost \
    --to=kernel@nn7.de \
    --cc=jb@jblache.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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;
as well as URLs for NNTP newsgroup(s).