[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9fc96bce-630d-3f2c-eab7-1270251fbb5b@infradead.org>
Date: Fri, 27 Jan 2023 15:01:25 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Daniel Bristot de Oliveira <bristot@...nel.org>,
linux-kernel@...r.kernel.org
Cc: Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-trace-kernel@...r.kernel.org,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Suzuki K Poulose <suzuki.poulose@....com>,
coresight@...ts.linaro.org, linux-arm-kernel@...ts.infradead.org,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH 31/35] Documentation: trace: correct spelling
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
Powered by blists - more mailing lists