mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux RCU <rcu@vger.kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
	Joel Fernandes <joelagnelf@nvidia.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Zqiang <qiang.zhang@linux.dev>
Subject: Re: [PATCH] Documentation: RCU: Wrap kvm-remote.sh rerun snippet in literal code block
Date: Mon, 18 Aug 2025 21:16:04 -0700	[thread overview]
Message-ID: <f36daf4d-ed4b-4ac2-9932-10e46abdc109@infradead.org> (raw)
In-Reply-To: <20250819004559.11429-1-bagasdotme@gmail.com>



On 8/18/25 5:45 PM, Bagas Sanjaya wrote:
> Unlike other kvm*.sh snippets in RCU torture test documentation,
> kvm-remote.sh rerun snippet isn't formatted as literal code block,
> causing it to be definition list instead in htmldocs output.
> 
> Wrap it like the rest.
> 
> Fixes: 0c208a793022 ("doc: Update torture.rst")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

BTW, 20 lines above this change, the text says:

  If you the following command works::

Do you have any idea what word is missing there?
or maybe Paul can make a suggestion.

Thanks.

> ---
>  Documentation/RCU/torture.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/RCU/torture.rst b/Documentation/RCU/torture.rst
> index 4b1f99c4181fee..cc57d01ed700ff 100644
> --- a/Documentation/RCU/torture.rst
> +++ b/Documentation/RCU/torture.rst
> @@ -364,7 +364,7 @@ systems must come first.
>  The kvm.sh ``--dryrun scenarios`` argument is useful for working out
>  how many scenarios may be run in one batch across a group of systems.
>  
> -You can also re-run a previous remote run in a manner similar to kvm.sh:
> +You can also re-run a previous remote run in a manner similar to kvm.sh::
>  
>  	kvm-remote.sh "system0 system1 system2 system3 system4 system5" \
>  		tools/testing/selftests/rcutorture/res/2022.11.03-11.26.28-remote \
> 
> base-commit: 61399e0c5410567ef60cb1cda34cca42903842e3

-- 
~Randy

  reply	other threads:[~2025-08-19  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  0:45 Bagas Sanjaya
2025-08-19  4:16 ` Randy Dunlap [this message]
2025-08-19 15:40   ` Paul E. McKenney

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=f36daf4d-ed4b-4ac2-9932-10e46abdc109@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bagasdotme@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dave@stgolabs.net \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joelagnelf@nvidia.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=neeraj.upadhyay@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang@linux.dev \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=urezki@gmail.com \
    /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®