From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Daniel Bristot de Oliveira <bristot@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 12:35:10 +0530 [thread overview]
Message-ID: <e5ecc40f-f8f8-ec6b-b8b8-fb7734878de8@quicinc.com> (raw)
In-Reply-To: <20230127064005.1558-32-rdunlap@infradead.org>
On 1/27/2023 12:10 PM, Randy Dunlap wrote:
> Correct spelling problems for Documentation/trace/ 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: Mathieu Poirier <mathieu.poirier@linaro.org>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: coresight@lists.linaro.org
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/trace/coresight/coresight-etm4x-reference.rst | 2 +-
> Documentation/trace/events.rst | 6 +++---
> Documentation/trace/fprobe.rst | 2 +-
> Documentation/trace/ftrace-uses.rst | 2 +-
> Documentation/trace/hwlat_detector.rst | 2 +-
> Documentation/trace/rv/runtime-verification.rst | 2 +-
> Documentation/trace/uprobetracer.rst | 2 +-
> 7 files changed, 9 insertions(+), 9 deletions(-)
>
> diff -- a/Documentation/trace/coresight/coresight-etm4x-reference.rst b/Documentation/trace/coresight/coresight-etm4x-reference.rst
> --- a/Documentation/trace/coresight/coresight-etm4x-reference.rst
> +++ b/Documentation/trace/coresight/coresight-etm4x-reference.rst
> @@ -675,7 +675,7 @@ Bit assignments shown below:-
> reconstructed using only conditional branches.
>
> There is currently no support in Perf for supplying modified binaries to the decoder, so this
> - feature is only inteded to be used for debugging purposes or with a 3rd party tool.
> + feature is only intended to be used for debugging purposes or with a 3rd party tool.
>
> Choosing this option will result in a significant increase in the amount of trace generated -
> possible danger of overflows, or fewer instructions covered. Note, that this option also
> diff -- a/Documentation/trace/events.rst b/Documentation/trace/events.rst
> --- a/Documentation/trace/events.rst
> +++ b/Documentation/trace/events.rst
> @@ -903,7 +903,7 @@ functions can be used.
>
> To create a kprobe event, an empty or partially empty kprobe event
> should first be created using kprobe_event_gen_cmd_start(). The name
> -of the event and the probe location should be specfied along with one
> +of the event and the probe location should be specified along with one
> or args each representing a probe field should be supplied to this
> function. Before calling kprobe_event_gen_cmd_start(), the user
> should create and initialize a dynevent_cmd object using
> @@ -983,7 +983,7 @@ The basic idea is simple and amounts to
> layer that can be used to generate trace event commands. The
> generated command strings can then be passed to the command-parsing
> and event creation code that already exists in the trace event
> -subystem for creating the corresponding trace events.
> +subsystem for creating the corresponding trace events.
>
> In a nutshell, the way it works is that the higher-level interface
> code creates a struct dynevent_cmd object, then uses a couple
> @@ -1056,7 +1056,7 @@ to add an operator between the pair (her
> appended onto the end of the arg pair (here ';').
>
> There's also a dynevent_str_add() function that can be used to simply
> -add a string as-is, with no spaces, delimeters, or arg check.
> +add a string as-is, with no spaces, delimiters, or arg check.
>
> Any number of dynevent_*_add() calls can be made to build up the string
> (until its length surpasses cmd->maxlen). When all the arguments have
> diff -- a/Documentation/trace/fprobe.rst b/Documentation/trace/fprobe.rst
> --- a/Documentation/trace/fprobe.rst
> +++ b/Documentation/trace/fprobe.rst
> @@ -111,7 +111,7 @@ saved at function entry and passed to ex
> the instruction pointer of @regs may be different from the @entry_ip
> in the entry_handler. If you need traced instruction pointer, you need
> to use @entry_ip. On the other hand, in the exit_handler, the instruction
> - pointer of @regs is set to the currect return address.
> + pointer of @regs is set to the correct return address.
>
> Share the callbacks with kprobes
> ================================
> diff -- a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst
> --- a/Documentation/trace/ftrace-uses.rst
> +++ b/Documentation/trace/ftrace-uses.rst
> @@ -193,7 +193,7 @@ FTRACE_OPS_FL_RECURSION
> Not, if this flag is set, then the callback will always be called
> with preemption disabled. If it is not set, then it is possible
> (but not guaranteed) that the callback will be called in
> - preemptable context.
> + preemptible context.
>
> FTRACE_OPS_FL_IPMODIFY
> Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack"
> diff -- a/Documentation/trace/hwlat_detector.rst b/Documentation/trace/hwlat_detector.rst
> --- a/Documentation/trace/hwlat_detector.rst
> +++ b/Documentation/trace/hwlat_detector.rst
> @@ -14,7 +14,7 @@ originally written for use by the "RT" p
> kernel is highly latency sensitive.
>
> SMIs are not serviced by the Linux kernel, which means that it does not
> -even know that they are occuring. SMIs are instead set up by BIOS code
> +even know that they are occurring. SMIs are instead set up by BIOS code
> and are serviced by BIOS code, usually for "critical" events such as
> management of thermal sensors and fans. Sometimes though, SMIs are used for
> other tasks and those tasks can spend an inordinate amount of time in the
> 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
> diff -- a/Documentation/trace/uprobetracer.rst b/Documentation/trace/uprobetracer.rst
> --- a/Documentation/trace/uprobetracer.rst
> +++ b/Documentation/trace/uprobetracer.rst
> @@ -55,7 +55,7 @@ Synopsis of uprobe_tracer
>
> (\*1) only for return probe.
> (\*2) this is useful for fetching a field of data structures.
> - (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe
> + (\*3) Unlike kprobe event, "u" prefix will just be ignored, because uprobe
> events can access only user-space memory.
>
> Types
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-27 7:05 UTC|newest]
Thread overview: 78+ 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:39 ` [PATCH 02/35] Documentation: arm: correct spelling Randy Dunlap
2023-01-27 6:55 ` Mukesh Ojha
2023-01-27 6:39 ` [PATCH 01/35] Documentation: arm64: " Randy Dunlap
2023-01-27 7:02 ` Mukesh Ojha
2023-01-27 6:39 ` [PATCH 03/35] Documentation: block: " Randy Dunlap
2023-01-27 8:31 ` Bagas Sanjaya
2023-01-27 22:58 ` Randy Dunlap
2023-01-27 8:36 ` Mukesh Ojha
2023-01-27 6:39 ` [PATCH 04/35] Documentation: bpf: " Randy Dunlap
2023-01-27 8:29 ` Bagas Sanjaya
2023-01-28 19:38 ` Alexei Starovoitov
2023-01-30 14:24 ` David Vernet
2023-01-30 14:26 ` David Vernet
2023-01-27 6:39 ` [PATCH 05/35] Documentation: core-api: " Randy Dunlap
2023-01-27 15:25 ` Mukesh Ojha
2023-01-27 6:39 ` [PATCH 06/35] Documentation: fault-injection: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 07/35] Documentation: fb: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 08/35] Documentation: features: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 09/35] Documentation: firmware-guide/acpi: " Randy Dunlap
2023-01-30 15:52 ` Rafael J. Wysocki
2023-01-27 6:39 ` [PATCH 10/35] Documentation: hid: " Randy Dunlap
2023-01-27 16:20 ` srinivas pandruvada
2023-02-06 14:01 ` (subset) " Benjamin Tissoires
2023-01-27 6:39 ` [PATCH 11/35] Documentation: i2c: " Randy Dunlap
2023-01-27 7:14 ` Wolfram Sang
2023-01-27 8:26 ` Bagas Sanjaya
2023-01-27 22:34 ` Randy Dunlap
2023-01-27 6:39 ` [PATCH 12/35] Documentation: input: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 13/35] Documentation: isdn: " Randy Dunlap
2023-01-28 6:06 ` Jakub Kicinski
2023-01-27 6:39 ` [PATCH 14/35] Documentation: leds: " Randy Dunlap
2023-01-27 9:30 ` Lee Jones
2023-01-27 6:39 ` [PATCH 15/35] Documentation: litmus-tests: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 16/35] Documentation: livepatch: " Randy Dunlap
2023-01-27 10:52 ` Petr Mladek
2023-01-27 6:39 ` [PATCH 17/35] Documentation: locking: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 18/35] Documentation: mm: " Randy Dunlap
2023-01-27 6:44 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-27 8:27 ` Bagas Sanjaya
2023-01-30 10:07 ` Mike Rapoport
2023-01-27 6:39 ` [PATCH 19/35] Documentation: openrisc: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 20/35] Documentation: PCI: " Randy Dunlap
2023-01-27 15:55 ` Bjorn Helgaas
2023-01-27 6:39 ` [PATCH 22/35] Documentation: power: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 21/35] Documentation: powerpc: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 23/35] Documentation: s390: " Randy Dunlap
2023-01-27 11:43 ` Heiko Carstens
2023-01-27 6:39 ` [PATCH 24/35] Documentation: scheduler: " Randy Dunlap
2023-01-27 15:33 ` Mukesh Ojha
2023-01-27 6:39 ` [PATCH 25/35] Documentation: security: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 26/35] Documentation: sound: " Randy Dunlap
2023-01-29 8:24 ` Takashi Iwai
2023-01-27 6:39 ` [PATCH 27/35] Documentation: spi: " Randy Dunlap
2023-01-27 6:39 ` [PATCH 28/35] Documentation: target: " Randy Dunlap
2023-02-08 23:13 ` Martin K. Petersen
2023-01-27 6:39 ` [PATCH 29/35] Documentation: timers: " Randy Dunlap
2023-01-27 6:40 ` [PATCH 30/35] Documentation: tools/rtla: " Randy Dunlap
2023-01-27 8:52 ` Daniel Bristot de Oliveira
2023-01-27 19:53 ` Steven Rostedt
2023-01-27 6:40 ` [PATCH 31/35] Documentation: trace: " Randy Dunlap
2023-01-27 7:05 ` Mukesh Ojha [this message]
2023-01-27 8:54 ` Daniel Bristot de Oliveira
2023-01-27 23:01 ` Randy Dunlap
2023-01-27 19:54 ` Steven Rostedt
2023-01-31 18:20 ` Suzuki K Poulose
2023-01-27 6:40 ` [PATCH 32/35] Documentation: usb: " Randy Dunlap
2023-01-27 6:40 ` [PATCH 33/35] Documentation: w1: " Randy Dunlap
2023-01-27 6:40 ` [PATCH 34/35] Documentation: x86: " Randy Dunlap
2023-01-27 6:40 ` [PATCH 35/35] Documentation: xtensa: " Randy Dunlap
2023-01-27 17:45 ` Max Filippov
2023-01-27 6:59 ` [PATCH 15/35] Documentation: litmus-tests: " David Howells
2023-01-27 14:59 ` Paul E. McKenney
2023-01-27 6:59 ` [PATCH 25/35] Documentation: security: " David Howells
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=e5ecc40f-f8f8-ec6b-b8b8-fb7734878de8@quicinc.com \
--to=quic_mojha@quicinc.com \
--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=rdunlap@infradead.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).