From: akpm@linux-foundation.org
To: dbaryshkov@gmail.com, rpurdie@rpsys.net, mm-commits@vger.kernel.org
Subject: - leds-make-sure-led-trigger-is-valid-before-calling-trigger-activate.patch removed from -mm tree
Date: Fri, 18 Jul 2008 16:24:16 -0700 [thread overview]
Message-ID: <200807182324.m6INOGa9004181@imap1.linux-foundation.org> (raw)
The patch titled
leds: make sure led->trigger is valid before calling trigger->activate
has been removed from the -mm tree. Its filename was
leds-make-sure-led-trigger-is-valid-before-calling-trigger-activate.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: leds: make sure led->trigger is valid before calling trigger->activate
From: Dmitry Baryshkov <dbaryshkov@gmail.com>
Signed-off-by: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/leds/led-triggers.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/leds/led-triggers.c~leds-make-sure-led-trigger-is-valid-before-calling-trigger-activate drivers/leds/led-triggers.c
--- a/drivers/leds/led-triggers.c~leds-make-sure-led-trigger-is-valid-before-calling-trigger-activate
+++ a/drivers/leds/led-triggers.c
@@ -111,16 +111,17 @@ void led_trigger_set(struct led_classdev
flags);
if (led_cdev->trigger->deactivate)
led_cdev->trigger->deactivate(led_cdev);
+ led_cdev->trigger = NULL;
led_set_brightness(led_cdev, LED_OFF);
}
if (trigger) {
write_lock_irqsave(&trigger->leddev_list_lock, flags);
list_add_tail(&led_cdev->trig_list, &trigger->led_cdevs);
write_unlock_irqrestore(&trigger->leddev_list_lock, flags);
+ led_cdev->trigger = trigger;
if (trigger->activate)
trigger->activate(led_cdev);
}
- led_cdev->trigger = trigger;
}
EXPORT_SYMBOL_GPL(led_trigger_set);
_
Patches currently in -mm which might be from dbaryshkov@gmail.com are
origin.patch
linux-next.patch
reply other threads:[~2008-07-18 23:24 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=200807182324.m6INOGa9004181@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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