From: Bryan Wu <bryan.wu@canonical.com>
To: gregkh@linuxfoundation.org, ccross@android.com, hmh@hmh.eng.br,
rpurdie@rpsys.net, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: [PATCH 3/3] ledtrig-timer: convert to use device_create_file_uevent API
Date: Fri, 27 Jul 2012 12:02:43 +0800 [thread overview]
Message-ID: <1343361763-10307-4-git-send-email-bryan.wu@canonical.com> (raw)
In-Reply-To: <1343361763-10307-1-git-send-email-bryan.wu@canonical.com>
To send KOBJ_CHANGE uevent to userspace which is required by Android
Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
---
drivers/leds/ledtrig-timer.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/leds/ledtrig-timer.c b/drivers/leds/ledtrig-timer.c
index 9010f7a..d8b6296 100644
--- a/drivers/leds/ledtrig-timer.c
+++ b/drivers/leds/ledtrig-timer.c
@@ -78,10 +78,12 @@ static void timer_trig_activate(struct led_classdev *led_cdev)
led_cdev->trigger_data = NULL;
- rc = device_create_file(led_cdev->dev, &dev_attr_delay_on);
+ rc = device_create_file_uevent(led_cdev->dev, &dev_attr_delay_on,
+ "TRIGGER=timer", KOBJ_CHANGE);
if (rc)
return;
- rc = device_create_file(led_cdev->dev, &dev_attr_delay_off);
+ rc = device_create_file_uevent(led_cdev->dev, &dev_attr_delay_off,
+ "TRIGGER=timer", KOBJ_CHANGE);
if (rc)
goto err_out_delayon;
--
1.7.11.1
next prev parent reply other threads:[~2012-07-27 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 4:02 [PATCH 0/3] add new API to sysfs and device core code Bryan Wu
2012-07-27 4:02 ` [PATCH 1/3] sysfs: introduce a sysfs_create_file_uevent new API Bryan Wu
2012-07-27 15:52 ` Greg KH
2012-07-28 15:18 ` Bryan Wu
2012-07-27 4:02 ` [PATCH 2/3] drivers: add a new device_create_file_uevent API Bryan Wu
2012-07-27 4:02 ` Bryan Wu [this message]
2012-07-27 15:50 ` [PATCH 0/3] add new API to sysfs and device core code Greg KH
2012-07-27 19:38 ` Colin Cross
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=1343361763-10307-4-git-send-email-bryan.wu@canonical.com \
--to=bryan.wu@canonical.com \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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).