From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Kreimer <algonell@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Documentation/rv: Fix typos
Date: Tue, 10 Dec 2024 23:08:59 -0500 [thread overview]
Message-ID: <20241210230859.6b0d93b2@batman.local.home> (raw)
In-Reply-To: <20241209130640.10954-1-algonell@gmail.com>
On Mon, 9 Dec 2024 15:06:00 +0200
Andrew Kreimer <algonell@gmail.com> wrote:
> There are some typos in the documentation: 'a' -> 'at', missing 'to'.
> Fix them.
>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> ---
> Documentation/trace/rv/runtime-verification.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/rv/runtime-verification.rst b/Documentation/trace/rv/runtime-verification.rst
> index dae78dfa7cdc..c700dde9259c 100644
> --- a/Documentation/trace/rv/runtime-verification.rst
> +++ b/Documentation/trace/rv/runtime-verification.rst
> @@ -8,14 +8,14 @@ checking* and *theorem proving*) with a more practical approach for complex
> systems.
>
> Instead of relying on a fine-grained model of a system (e.g., a
> -re-implementation a instruction level), RV works by analyzing the trace of the
> +re-implementation at instruction level), RV works by analyzing the trace of the
> system's actual execution, comparing it against a formal specification of
> the system behavior.
>
> The main advantage is that RV can give precise information on the runtime
> behavior of the monitored system, without the pitfalls of developing models
> that require a re-implementation of the entire system in a modeling language.
> -Moreover, given an efficient monitoring method, it is possible execute an
> +Moreover, given an efficient monitoring method, it is possible to execute an
> *online* verification of a system, enabling the *reaction* for unexpected
> events, avoiding, for example, the propagation of a failure on safety-critical
> systems.
next prev parent reply other threads:[~2024-12-11 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 13:06 [PATCH] Documentation/rv: Fix typos Andrew Kreimer
2024-12-11 4:08 ` Steven Rostedt [this message]
2024-12-13 15:42 ` Jonathan Corbet
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=20241210230859.6b0d93b2@batman.local.home \
--to=rostedt@goodmis.org \
--cc=algonell@gmail.com \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@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