From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753654AbdFGXT0 (ORCPT ); Wed, 7 Jun 2017 19:19:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:35720 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752722AbdFGXTW (ORCPT ); Wed, 7 Jun 2017 19:19:22 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 979F2239D2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Date: Wed, 7 Jun 2017 20:19:14 -0300 From: Arnaldo Carvalho de Melo To: SeongJae Park Cc: peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/5] perf-script-python,perl.txt: Fix typos Message-ID: <20170607231914.GD6949@kernel.org> References: <20170530111827.21732-1-sj38.park@gmail.com> <20170530111827.21732-3-sj38.park@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170530111827.21732-3-sj38.park@gmail.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > 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