All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rodrigo Pereira <rodripe@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] leds-clevo-mail: extend naming convention of leds subsystem
Date: Sun, 28 Oct 2007 12:22:37 +0100	[thread overview]
Message-ID: <472470FD.90604@freemail.hu> (raw)

From: Márton Németh <nm127@freemail.hu>

Extend the leds subsystem naming convention with the "function"
property. For example a LED can indicate if a new mail has arrived.

Signed-off-by: Márton Németh <nm127@freemail.hu>
---
diff -uprN linux-2.6.24-rc1.a/Documentation/leds-class.txt linux-2.6.24-rc1.b/Documentation/leds-class.txt
--- linux-2.6.24-rc1.a/Documentation/leds-class.txt	2007-10-28 09:01:56.000000000 +0100
+++ linux-2.6.24-rc1.b/Documentation/leds-class.txt	2007-10-28 09:20:07.000000000 +0100
@@ -39,7 +39,9 @@ LED Device Naming

 Is currently of the form:

-"devicename:colour"
+"devicename:colour" or
+"devicename:colour:function" or
+"devicename::function"

 There have been calls for LED properties such as colour to be exported as
 individual led class attributes. As a solution which doesn't incur as much
diff -uprN linux-2.6.24-rc1.a/drivers/leds/leds-clevo-mail.c linux-2.6.24-rc1.b/drivers/leds/leds-clevo-mail.c
--- linux-2.6.24-rc1.a/drivers/leds/leds-clevo-mail.c	2007-10-28 10:18:42.000000000 +0100
+++ linux-2.6.24-rc1.b/drivers/leds/leds-clevo-mail.c	2007-10-28 10:18:56.000000000 +0100
@@ -93,7 +93,7 @@ static void clevo_mail_led_set(struct le
 }

 static struct led_classdev clevo_mail_led = {
-	.name			= "clevo",
+	.name			= "clevo::mail",
 	.brightness_set		= clevo_mail_led_set,
 };


                 reply	other threads:[~2007-10-28 10:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=472470FD.90604@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rodripe@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.