lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 23 Mar 2021 14:53:27 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, rostedt@...dmis.org,
        mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: Trivial typo fixes

On 3/23/21 1:33 PM, Bhaskar Chowdhury wrote:
> Trivial spelling fixes.
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Ingo has already fixed all of these.
Plus many more that are trace-related.

> ---
>  kernel/trace/trace_seq.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/trace/trace_seq.c b/kernel/trace/trace_seq.c
> index 1d84fcc78e3e..e03eae7a5577 100644
> --- a/kernel/trace/trace_seq.c
> +++ b/kernel/trace/trace_seq.c
> @@ -12,11 +12,11 @@
>   * This will set up the counters within the descriptor. You can call
>   * trace_seq_init() more than once to reset the trace_seq to start
>   * from scratch.
>   * The buffer size is currently PAGE_SIZE, although it may become dynamic
>   * in the future.
>   *
> - * A write to the buffer will either succed or fail. That is, unlike
> + * A write to the buffer will either succeed or fail. That is, unlike
>   * sprintf() there will not be a partial write (well it may write into
>   * the buffer but it wont update the pointers). This allows users to
>   * try to write something into the trace_seq buffer and if it fails
> @@ -73,7 +73,7 @@ int trace_print_seq(struct seq_file *m, struct trace_seq *s)
>   * @fmt: printf format string
>   *
>   * The tracer may use either sequence operations or its own
> - * copy to user routines. To simplify formating of a trace
> + * copy to user routines. To simplify formatting of a trace
>   * trace_seq_printf() is used to store strings into a special
>   * buffer (@s). Then the output may be either used by
>   * the sequencer or pulled into another buffer.
> @@ -133,7 +133,7 @@ EXPORT_SYMBOL_GPL(trace_seq_bitmask);
>   * @fmt: printf format string
>   *
>   * The tracer may use either sequence operations or its own
> - * copy to user routines. To simplify formating of a trace
> + * copy to user routines. To simplify formatting of a trace
>   * trace_seq_printf is used to store strings into a special
>   * buffer (@s). Then the output may be either used by
>   * the sequencer or pulled into another buffer.
> @@ -226,7 +226,7 @@ EXPORT_SYMBOL_GPL(trace_seq_puts);
>   * @c: simple character to record
>   *
>   * The tracer may use either the sequence operations or its own
> - * copy to user routines. This function records a simple charater
> + * copy to user routines. This function records a simple character
>   * into a special buffer (@s) for later retrieval by a sequencer
>   * or other mechanism.
>   */
> @@ -348,7 +348,7 @@ int trace_seq_path(struct trace_seq *s, const struct path *path)
>  EXPORT_SYMBOL_GPL(trace_seq_path);
> 
>  /**
> - * trace_seq_to_user - copy the squence buffer to user space
> + * trace_seq_to_user - copy the sequence buffer to user space
>   * @s: trace sequence descriptor
>   * @ubuf: The userspace memory location to copy to
>   * @cnt: The amount to copy
> --


-- 
~Randy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ