From: Alexander Dahl <ada@thorsis.com>
To: linux-doc@vger.kernel.org, linux-leds@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Fabio Baltieri <fabio.baltieri@gmail.com>
Subject: [PATCH] docs: leds: ledtrig-oneshot: Fix spelling mistake
Date: Tue, 18 Apr 2023 13:34:02 +0200 [thread overview]
Message-ID: <20230418113402.188391-1-ada@thorsis.com> (raw)
It's no comparision, but a "first this, then that" situation.
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
Documentation/leds/ledtrig-oneshot.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/leds/ledtrig-oneshot.rst b/Documentation/leds/ledtrig-oneshot.rst
index 69fa3ea1d554..e044d69e9c0f 100644
--- a/Documentation/leds/ledtrig-oneshot.rst
+++ b/Documentation/leds/ledtrig-oneshot.rst
@@ -5,7 +5,7 @@ One-shot LED Trigger
This is a LED trigger useful for signaling the user of an event where there are
no clear trap points to put standard led-on and led-off settings. Using this
trigger, the application needs only to signal the trigger when an event has
-happened, than the trigger turns the LED on and than keeps it off for a
+happened, then the trigger turns the LED on and then keeps it off for a
specified amount of time.
This trigger is meant to be usable both for sporadic and dense events. In the
base-commit: 6a8f57ae2eb07ab39a6f0ccad60c760743051026
--
2.30.2
next reply other threads:[~2023-04-18 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 11:34 Alexander Dahl [this message]
2023-04-18 11:46 ` Pavel Machek
2023-04-20 14:00 ` Lee Jones
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=20230418113402.188391-1-ada@thorsis.com \
--to=ada@thorsis.com \
--cc=corbet@lwn.net \
--cc=fabio.baltieri@gmail.com \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®