linux-kernel - Re: [PATCH 2/5] perf-script-python,perl.txt: Fix typos

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]

Message-ID: <20170607231914.GD6949@kernel.org>
Date:   Wed, 7 Jun 2017 20:19:14 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     SeongJae Park <sj38.park@...il.com>
Cc:     peterz@...radead.org, mingo@...hat.com,
        alexander.shishkin@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] perf-script-python,perl.txt: Fix typos

Em Tue, May 30, 2017 at 08:18:24PM +0900, SeongJae Park escreveu:
> This commit fixes two typos in documents for perf-script-python and
> perf-script-perl as below:
> 
> - /sys/kernel/debug/tracing events -> /sys/kernel/debug/tracing/events/
> - trace_handled -> trace_unhandled

Thanks, applied to perf/urgent.

- Arnaldo
 
> Signed-off-by: SeongJae Park <sj38.park@...il.com>
> Fixes: cff68e582237 ("perf/scripts: Add perf-trace-python Documentation")
> ---
>  tools/perf/Documentation/perf-script-perl.txt   | 2 +-
>  tools/perf/Documentation/perf-script-python.txt | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-script-perl.txt b/tools/perf/Documentation/perf-script-perl.txt
> index dfbb506d2c34..142606c0ec9c 100644
> --- a/tools/perf/Documentation/perf-script-perl.txt
> +++ b/tools/perf/Documentation/perf-script-perl.txt
> @@ -39,7 +39,7 @@ EVENT HANDLERS
>  When perf script is invoked using a trace script, a user-defined
>  'handler function' is called for each event in the trace.  If there's
>  no handler function defined for a given event type, the event is
> -ignored (or passed to a 'trace_handled' function, see below) and the
> +ignored (or passed to a 'trace_unhandled' function, see below) and the
>  next event is processed.
>  
>  Most of the event's field values are passed as arguments to the
> diff --git a/tools/perf/Documentation/perf-script-python.txt b/tools/perf/Documentation/perf-script-python.txt
> index 54acba221558..087b87c956ba 100644
> --- a/tools/perf/Documentation/perf-script-python.txt
> +++ b/tools/perf/Documentation/perf-script-python.txt
> @@ -321,7 +321,7 @@ So those are the essential steps in writing and running a script.  The
>  process can be generalized to any tracepoint or set of tracepoints
>  you're interested in - basically find the tracepoint(s) you're
>  interested in by looking at the list of available events shown by
> -'perf list' and/or look in /sys/kernel/debug/tracing events for
> +'perf list' and/or look in /sys/kernel/debug/tracing/events/ for
>  detailed event and field info, record the corresponding trace data
>  using 'perf record', passing it the list of interesting events,
>  generate a skeleton script using 'perf script -g python' and modify the
> @@ -437,7 +437,7 @@ EVENT HANDLERS
>  When perf script is invoked using a trace script, a user-defined
>  'handler function' is called for each event in the trace.  If there's
>  no handler function defined for a given event type, the event is
> -ignored (or passed to a 'trace_handled' function, see below) and the
> +ignored (or passed to a 'trace_unhandled' function, see below) and the
>  next event is processed.
>  
>  Most of the event's field values are passed as arguments to the
> -- 
> 2.13.0