Re: [PATCH 2/4] docs: admin-guide: fix stress-ng command examples

[Shuah Khan]

On 5/3/26 04:14, Cheng-Han Wu wrote:
> The workload tracing guide includes stress-ng command examples with a
> stray "command." word at the end. This makes the examples invalid if they
> are copied and run directly.
>
> Remove the stray word from the stress-ng example. Also use "--" in the
> perf record example to clearly separate perf record options from the
> workload command being recorded.
>
> Signed-off-by: Cheng-Han Wu <hank20010209@xxxxxxxxx>
> ---
>   Documentation/admin-guide/workload-tracing.rst | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/workload-tracing.rst b/Documentation/admin-guide/workload-tracing.rst
> index 22cb05025ffc..43a3c8098654 100644
> --- a/Documentation/admin-guide/workload-tracing.rst
> +++ b/Documentation/admin-guide/workload-tracing.rst
> @@ -271,7 +271,7 @@ exercised:
>   
>   The following command runs the stressor::
>   
> -  stress-ng --netdev 1 -t 60 --metrics command.
> +  stress-ng --netdev 1 -t 60 --metrics
>   
>   We can use the perf record command to record the events and information
>   associated with a process. This command records the profiling data in the
> @@ -281,7 +281,7 @@ Using the following commands you can record the events associated with the
>   netdev stressor, view the generated report perf.data and annotate the output
>   to view the statistics of each instruction of the program::
>   
> -  perf record stress-ng --netdev 1 -t 60 --metrics command.
> +  perf record -- stress-ng --netdev 1 -t 60 --metrics
>     perf report
>     perf annotate
>   

Looks to good to me.

Reviewed-by: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>

thanks,
-- Shuah