From: Shuah Khan <skhan@linuxfoundation.org>
To: "Yo-Jung (Leo) Lin" <0xff07@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Documentation: kselftest: fix codeblock
Date: Fri, 3 May 2024 12:59:54 -0600 [thread overview]
Message-ID: <6a54d332-c13f-4d9c-93c7-7700baf951f9@linuxfoundation.org> (raw)
In-Reply-To: <20240429165047.16088-1-0xff07@gmail.com>
On 4/29/24 10:50, Yo-Jung (Leo) Lin wrote:
> Add extra colon to mark command in the next paragraph as codeblock
>
> Signed-off-by: Yo-Jung (Leo) Lin <0xff07@gmail.com>
> ---
> Documentation/dev-tools/kselftest.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kselftest.rst b/Documentation/dev-tools/kselftest.rst
> index ff10dc6eef5d..dcf634e411bd 100644
> --- a/Documentation/dev-tools/kselftest.rst
> +++ b/Documentation/dev-tools/kselftest.rst
> @@ -183,7 +183,7 @@ expected time it takes to run a test. If you have control over the systems
> which will run the tests you can configure a test runner on those systems to
> use a greater or lower timeout on the command line as with the `-o` or
> the `--override-timeout` argument. For example to use 165 seconds instead
> -one would use:
> +one would use::
>
> $ ./run_kselftest.sh --override-timeout 165
>
Thank you. Applied to linux=kselftest next for Linux 6.10-rc1.
thanks,
-- Shuah
prev parent reply other threads:[~2024-05-03 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 16:50 [PATCH] Documentation: kselftest: fix codeblock Yo-Jung (Leo) Lin
2024-05-03 18:59 ` Shuah Khan [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=6a54d332-c13f-4d9c-93c7-7700baf951f9@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=0xff07@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).