All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@kernel.org>, 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>
Subject: Re: [PATCH perf/core] perf tools: Add missing break for PERF_RECORD_ITRACE_START
Date: Mon, 29 Jun 2015 10:05:49 -0300	[thread overview]
Message-ID: <20150629130549.GA11747@kernel.org> (raw)
In-Reply-To: <20150629114714.GG19282@twins.programming.kicks-ass.net>

Em Mon, Jun 29, 2015 at 01:47:14PM +0200, Peter Zijlstra escreveu:
> On Mon, Jun 29, 2015 at 02:17:18PM +0300, Adrian Hunter wrote:
> > On 29/06/15 14:12, Jiri Olsa wrote:
> > > +++ 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?
 
> I would tend to agree, its a very odd style.

Humm, there are two cases in tools/perf/, where it was made (hey, I am
to blame) for really simple stuff like:

    case A: B(); break;

To make it more compact.

But I just checked and this is not that uncommon:

  [acme@zoo linux]$ find . -name "*.[ch]" | xargs grep ';.*break'  | wc -l
  5035
  [acme@zoo linux]$ find arch -name "*.[ch]" | xargs grep ';.*break' | wc -l
  1440
  [acme@zoo linux]$ find block -name "*.[ch]" | xargs grep ';.*break' | wc -l
  7
  [acme@zoo linux]$ find crypto -name "*.[ch]" | xargs grep ';.*break' | wc -l
  0
  [acme@zoo linux]$ find fs -name "*.[ch]" | xargs grep ';.*break' | wc -l
  66
  [acme@zoo linux]$ find kernel -name "*.[ch]" | xargs grep ';.*break' | wc -l
  11
  [acme@zoo linux]$ find mm -name "*.[ch]" | xargs grep ';.*break' | wc -l
  3
  [acme@zoo linux]$

But I am not that attached to it, as said, just two cases :)

- Arnaldo

  reply	other threads:[~2015-06-29 13:06 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
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 [this message]
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=20150629130549.GA11747@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --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 \
    --cc=peterz@infradead.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.