From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Jiri Kosina <trivial@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>,
Willy Tarreau <w@1wt.eu>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/trivial] ledtrig-activity: Grammar s/a immediate/an immediate/
Date: Fri, 1 Dec 2017 21:14:43 +0100 [thread overview]
Message-ID: <71729f17-086f-171a-fa19-2c5cae5fecad@gmail.com> (raw)
In-Reply-To: <1512049001-19669-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
On 11/30/2017 02:36 PM, Geert Uytterhoeven wrote:
> Fixes: 7df4f9a9f0667ee6 ("leds: ledtrig-activity: Add a system activity LED trigger")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/leds/trigger/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
> index bb090216b4dc338d..6dac48c457d17ca5 100644
> --- a/drivers/leds/trigger/Kconfig
> +++ b/drivers/leds/trigger/Kconfig
> @@ -81,7 +81,7 @@ config LEDS_TRIGGER_ACTIVITY
> tristate "LED activity Trigger"
> depends on LEDS_TRIGGERS
> help
> - This allows LEDs to be controlled by a immediate CPU usage.
> + This allows LEDs to be controlled by an immediate CPU usage.
> The flash frequency and duty cycle varies from faint flashes to
> intense brightness depending on the instant CPU load.
> If unsure, say N.
>
Applied, thanks.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-12-01 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 13:36 [PATCH/trivial] ledtrig-activity: Grammar s/a immediate/an immediate/ Geert Uytterhoeven
2017-11-30 15:05 ` Pavel Machek
2017-12-01 20:14 ` Jacek Anaszewski [this message]
2017-12-01 20:21 ` Willy Tarreau
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=71729f17-086f-171a-fa19-2c5cae5fecad@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=trivial@kernel.org \
--cc=w@1wt.eu \
/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).