mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Colin King <colin.king@canonical.com>,
	Jerry Hoemann <jerry.hoemann@hpe.com>,
	linux-kselftest@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah <shuah@kernel.org>
Subject: Re: [PATCH][next] selftests: watchdog: fix spelling mistake "experies" -> "expires"
Date: Thu, 13 Dec 2018 07:24:51 -0700	[thread overview]
Message-ID: <32532eac-969a-83e2-4373-fdbef613ce33@kernel.org> (raw)
In-Reply-To: <20181213094015.31397-1-colin.king@canonical.com>

On 12/13/18 2:40 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in the --gettimeleft help text, fix it.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   tools/testing/selftests/watchdog/watchdog-test.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/watchdog/watchdog-test.c b/tools/testing/selftests/watchdog/watchdog-test.c
> index dac907a932ce..c2333c78cf04 100644
> --- a/tools/testing/selftests/watchdog/watchdog-test.c
> +++ b/tools/testing/selftests/watchdog/watchdog-test.c
> @@ -78,7 +78,7 @@ static void usage(char *progname)
>   	printf(" -T, --gettimeout    Get the timeout\n");
>   	printf(" -n, --pretimeout=T  Set the pretimeout to T seconds\n");
>   	printf(" -N, --getpretimeout Get the pretimeout\n");
> -	printf(" -L, --gettimeleft   Get the time left until timer experies\n");
> +	printf(" -L, --gettimeleft   Get the time left until timer expires\n");
>   	printf("\n");
>   	printf("Parameters are parsed left-to-right in real-time.\n");
>   	printf("Example: %s -d -t 10 -p 5 -e\n", progname);
> 

That is quick! Thanks for the patch. I will apply it to linuxk-kselftest 
next

thanks,
-- Shuah

      reply	other threads:[~2018-12-13 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13  9:40 Colin King
2018-12-13 14:24 ` shuah [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=32532eac-969a-83e2-4373-fdbef613ce33@kernel.org \
    --to=shuah@kernel.org \
    --cc=colin.king@canonical.com \
    --cc=jerry.hoemann@hpe.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.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

all inboxes | Powered by JetHome®