From: Bryan Wu <bryan.wu@canonical.com>
To: rpurdie@rpsys.net, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org
Subject: [PATCH 2/2] Documentation: leds-class: fix a typo
Date: Tue, 6 Sep 2011 03:09:46 +0800 [thread overview]
Message-ID: <1315249786-15387-2-git-send-email-bryan.wu@canonical.com> (raw)
In-Reply-To: <1315249786-15387-1-git-send-email-bryan.wu@canonical.com>
Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
---
Documentation/leds/leds-class.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/leds/leds-class.txt b/Documentation/leds/leds-class.txt
index 4996586..79699c2 100644
--- a/Documentation/leds/leds-class.txt
+++ b/Documentation/leds/leds-class.txt
@@ -61,8 +61,8 @@ Hardware accelerated blink of LEDs
Some LEDs can be programmed to blink without any CPU interaction. To
support this feature, a LED driver can optionally implement the
blink_set() function (see <linux/leds.h>). To set an LED to blinking,
-however, it is better to use use the API function led_blink_set(),
-as it will check and implement software fallback if necessary.
+however, it is better to use the API function led_blink_set(), as it
+will check and implement software fallback if necessary.
To turn off blinking again, use the API function led_brightness_set()
as that will not just set the LED brightness but also stop any software
--
1.7.4.1
next prev parent reply other threads:[~2011-09-05 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:09 [PATCH 1/2] leds-class: change back LEDS_CLASS to tristate instead of bool Bryan Wu
2011-09-05 19:09 ` Bryan Wu [this message]
2011-09-05 19:52 ` [PATCH 2/2] Documentation: leds-class: fix a typo Richard Purdie
2011-09-07 18:56 ` Randy Dunlap
2011-09-08 17:11 ` Randy Dunlap
2011-09-05 19:51 ` [PATCH 1/2] leds-class: change back LEDS_CLASS to tristate instead of bool Richard Purdie
2011-09-05 20:49 ` Bryan Wu
2011-09-29 8:07 ` Russell King - ARM Linux
2011-09-30 9:09 ` Bryan Wu
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=1315249786-15387-2-git-send-email-bryan.wu@canonical.com \
--to=bryan.wu@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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
all inboxes | Powered by JetHome®