From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Baolin Wang <baolin.wang@linaro.org>,
Jiri Kosina <trivial@kernel.org>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] Documentation: ABI: led-trigger-pattern: Fix typos
Date: Wed, 7 Nov 2018 21:45:35 +0100 [thread overview]
Message-ID: <58507e6b-a1a9-c1ff-e469-11611ba7e8ab@gmail.com> (raw)
In-Reply-To: <20181107134524.13989-1-geert+renesas@glider.be>
Hi Geert,
On 11/07/2018 02:45 PM, Geert Uytterhoeven wrote:
> - Spelling s/brigntess/brightness/,
> - Double "use".
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/ABI/testing/sysfs-class-led-trigger-pattern | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> index fb3d1e03b8819bb9..1e5d172e064624d9 100644
> --- a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> @@ -37,8 +37,8 @@ Description:
> 0-| / \/ \/
> +---0----1----2----3----4----5----6------------> time (s)
>
> - 2. To make the LED go instantly from one brigntess value to another,
> - we should use use zero-time lengths (the brightness must be same as
> + 2. To make the LED go instantly from one brightness value to another,
> + we should use zero-time lengths (the brightness must be same as
> the previous tuple's). So the format should be:
> "brightness_1 duration_1 brightness_1 0 brightness_2 duration_2
> brightness_2 0 ...". For example:
>
Thanks for the patch.
Applied to the fixes-for-4.20-rc2 branch of linux-leds.git.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2018-11-07 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 13:45 [PATCH trivial] Documentation: ABI: led-trigger-pattern: Fix typos Geert Uytterhoeven
2018-11-07 14:11 ` Pavel Machek
2018-11-07 20:45 ` Jacek Anaszewski [this message]
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=58507e6b-a1a9-c1ff-e469-11611ba7e8ab@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=trivial@kernel.org \
/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