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.
 
 	- hide: echo nofuncgraph-cpu > trace_options
-- 
2.25.1

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