From: Randy Dunlap <rdunlap@infradead.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 31/35] Documentation: trace: correct spelling
Date: Fri, 27 Jan 2023 15:01:25 -0800 [thread overview]
Message-ID: <9fc96bce-630d-3f2c-eab7-1270251fbb5b@infradead.org> (raw)
In-Reply-To: <5c1d8862-4ee6-bd17-1a61-ec32689d0578@kernel.org>
On 1/27/23 00:54, Daniel Bristot de Oliveira wrote:
> On 1/27/23 07:40, Randy Dunlap wrote:
>> --- 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
>
> Do you mind making the rv part an independent patch?
>
> Spiting it helps in the backport of the fix to stable/distro kernels.
I wouldn't expect this to be packported. stable-kernel-rules.rst says:
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
--
~Randy
next prev parent reply other threads:[~2023-01-27 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-01-27 6:40 ` [PATCH 31/35] Documentation: trace: correct spelling Randy Dunlap
2023-01-27 7:05 ` Mukesh Ojha
2023-01-27 8:54 ` Daniel Bristot de Oliveira
2023-01-27 23:01 ` Randy Dunlap [this message]
2023-01-27 19:54 ` Steven Rostedt
2023-01-31 18:20 ` Suzuki K Poulose
2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown
2023-01-28 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
2023-02-14 16:57 ` Martin K. Petersen
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=9fc96bce-630d-3f2c-eab7-1270251fbb5b@infradead.org \
--to=rdunlap@infradead.org \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).