From: Adrian Hunter <adrian.hunter@intel.com>
To: Jiri Olsa <jolsa@kernel.org>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Kan Liang <kan.liang@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH perf/core] perf tools: Add missing break for PERF_RECORD_ITRACE_START
Date: Mon, 29 Jun 2015 14:17:18 +0300 [thread overview]
Message-ID: <5591293E.80308@intel.com> (raw)
In-Reply-To: <1435576340-19346-1-git-send-email-jolsa@kernel.org>
On 29/06/15 14:12, Jiri Olsa wrote:
> Missing switch break since introduction of new event:
> c4937a91ea56 perf tools: handle PERF_RECORD_LOST_SAMPLES
>
> Cc: Kan Liang <kan.liang@intel.com>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Link: http://lkml.kernel.org/n/tip-e3gbrp2561x2s9tkqvf2wh9n@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> tools/perf/util/machine.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index 4744673aff1b..a08e38339cac 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1448,7 +1448,7 @@ int machine__process_event(struct machine *machine, union perf_event *event,
> case PERF_RECORD_AUX:
> ret = machine__process_aux_event(machine, event); break;
> case PERF_RECORD_ITRACE_START:
> - ret = machine__process_itrace_start_event(machine, event);
> + ret = machine__process_itrace_start_event(machine, event); break;
> case PERF_RECORD_LOST_SAMPLES:
> ret = machine__process_lost_samples_event(machine, event, sample); break;
> break;
But now you have break; break;
Isn't putting 'break' on the end of the line making things harder to read?
next prev parent reply other threads:[~2015-06-29 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 11:12 [PATCH perf/core] perf tools: Add missing break for PERF_RECORD_ITRACE_START Jiri Olsa
2015-06-29 11:17 ` Adrian Hunter [this message]
2015-06-29 11:27 ` [PATCHv2 " Jiri Olsa
2015-06-29 20:17 ` Arnaldo Carvalho de Melo
2015-07-03 7:47 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2015-06-29 11:47 ` [PATCH perf/core] " Peter Zijlstra
2015-06-29 13:05 ` Arnaldo Carvalho de Melo
2015-06-29 11:23 ` Joe Perches
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=5591293E.80308@intel.com \
--to=adrian.hunter@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.