From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
linux-trace-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH 20/24] Documentation: trace/rv: correct spelling
Date: Wed, 8 Feb 2023 23:13:56 -0800 [thread overview]
Message-ID: <20230209071400.31476-21-rdunlap@infradead.org> (raw)
In-Reply-To: <20230209071400.31476-1-rdunlap@infradead.org>
Correct spelling problems for Documentation/trace/rv/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/trace/rv/runtime-verification.rst | 2 +-
diff -- a/Documentation/trace/rv/runtime-verification.rst b/Documentation/trace/rv/runtime-verification.rst
--- a/Documentation/trace/rv/runtime-verification.rst
+++ b/Documentation/trace/rv/runtime-verification.rst
@@ -31,7 +31,7 @@ In Linux terms, the runtime verification
*RV monitor* abstraction. A *RV monitor* includes a reference model of the
system, a set of instances of the monitor (per-cpu monitor, per-task monitor,
and so on), and the helper functions that glue the monitor to the system via
-trace, as depicted bellow::
+trace, as depicted below::
Linux +---- RV Monitor ----------------------------------+ Formal
Realm | | Realm
next prev parent reply other threads:[~2023-02-09 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:13 [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-02-09 7:13 ` Randy Dunlap [this message]
2023-02-09 11:45 ` [PATCH 20/24] Documentation: trace/rv: correct spelling Daniel Bristot de Oliveira
2023-02-10 21:37 ` Steven Rostedt
2023-02-09 7:13 ` [PATCH 21/24] Documentation: trace: " Randy Dunlap
2023-02-09 11:40 ` Mike Leach
2023-02-09 11:46 ` Daniel Bristot de Oliveira
2023-02-09 14:41 ` Masami Hiramatsu
2023-02-10 21:39 ` Steven Rostedt
2023-02-11 0:30 ` [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) patchwork-bot+netdevbpf
2023-06-26 6:56 ` Krzysztof Wilczyński
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=20230209071400.31476-21-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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 NNTP newsgroup(s).