public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Yuanhsi Chung <freshliver.cys@gmail.com>, rostedt@goodmis.org
Cc: mingo@redhat.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Yuanhsi Chung <freshliver.cys@gmail.com>
Subject: Re: [PATCH] Documentation: Fix filename typo in ftrace doc
Date: Fri, 17 Nov 2023 09:07:14 -0700	[thread overview]
Message-ID: <871qcoxt1p.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231104103329.215139-1-freshliver.cys@gmail.com>

Yuanhsi Chung <freshliver.cys@gmail.com> writes:

> The filename for setting the cpumask should be `tracing_cpumask`,
> instead of `tracing_cpu_mask`.
>
> Signed-off-by: Yuanhsi Chung <freshliver.cys@gmail.com>
> ---
>  Documentation/trace/ftrace.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index b37dc19e4d40..b93f11c430a9 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -2524,7 +2524,7 @@ want, depending on your needs.
>  
>  - The cpu number on which the function executed is default
>    enabled.  It is sometimes better to only trace one cpu (see
> -  tracing_cpu_mask file) or you might sometimes see unordered
> +  tracing_cpumask file) or you might sometimes see unordered
>    function calls while cpu tracing switch.

Applied, thanks.

jon

      reply	other threads:[~2023-11-17 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 10:33 [PATCH] Documentation: Fix filename typo in ftrace doc Yuanhsi Chung
2023-11-17 16:07 ` Jonathan Corbet [this message]

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=871qcoxt1p.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=freshliver.cys@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /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