All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	rostedt@goodmis.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Trivial typo fixes
Date: Tue, 23 Mar 2021 14:53:27 -0700	[thread overview]
Message-ID: <c9589765-b5cd-7cb5-4af5-2f7760a0a7a0@infradead.org> (raw)
In-Reply-To: <20210323203317.31944-1-unixbhaskar@gmail.com>

On 3/23/21 1:33 PM, Bhaskar Chowdhury wrote:
> Trivial spelling fixes.
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.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


  reply	other threads:[~2021-03-23 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 20:33 [PATCH] tracing: Trivial typo fixes Bhaskar Chowdhury
2021-03-23 21:53 ` Randy Dunlap [this message]
2021-03-23 22:05   ` Bhaskar Chowdhury

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=c9589765-b5cd-7cb5-4af5-2f7760a0a7a0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=unixbhaskar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.