From: Jonathan Corbet <corbet@lwn.net>
To: Gopi Krishna Menon <krishnagopi487@gmail.com>, rostedt@goodmis.org
Cc: Gopi Krishna Menon <krishnagopi487@gmail.com>,
skhan@linuxfoundation.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] Documentation/rv: Fix minor typo in monitor_synthesis page
Date: Tue, 12 Aug 2025 12:41:29 -0600 [thread overview]
Message-ID: <87zfc4e61y.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250810111249.93181-1-krishnagopi487@gmail.com>
Gopi Krishna Menon <krishnagopi487@gmail.com> writes:
> Specifically, fix spelling of "practice"
>
> Signed-off-by: Gopi Krishna Menon <krishnagopi487@gmail.com>
> ---
> Documentation/trace/rv/monitor_synthesis.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/rv/monitor_synthesis.rst b/Documentation/trace/rv/monitor_synthesis.rst
> index ac808a7554f5..3a7d7b2f6cb6 100644
> --- a/Documentation/trace/rv/monitor_synthesis.rst
> +++ b/Documentation/trace/rv/monitor_synthesis.rst
> @@ -181,7 +181,7 @@ which is the list of atomic propositions present in the LTL specification
> functions interacting with the Buchi automaton.
>
> While generating code, `rvgen` cannot understand the meaning of the atomic
> -propositions. Thus, that task is left for manual work. The recommended pratice
> +propositions. Thus, that task is left for manual work. The recommended practice
> is adding tracepoints to places where the atomic propositions change; and in the
Applied, thanks.
jon
next prev parent reply other threads:[~2025-08-12 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 11:12 [PATCH] Documentation/rv: Fix minor typo in monitor_synthesis page Gopi Krishna Menon
2025-08-12 18:41 ` Jonathan Corbet [this message]
2025-08-18 8:02 ` Gabriele Monaco
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=87zfc4e61y.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=krishnagopi487@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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