public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Ahern <dsahern@gmail.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
	peterz@infradead.org, fweisbec@gmail.com, paulus@samba.org,
	tglx@linutronix.de
Subject: Re: [PATCH] perf-record: no build id option fails
Date: Tue, 7 Feb 2012 10:06:23 +0100	[thread overview]
Message-ID: <20120207090622.GC15359@elte.hu> (raw)
In-Reply-To: <1328567272-13190-1-git-send-email-dsahern@gmail.com>


* David Ahern <dsahern@gmail.com> wrote:

> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -504,9 +504,9 @@ static int __cmd_record(struct perf_record *rec, int argc, const char **argv)
>  			return err;
>  	}
>  
> -	if (!!rec->no_buildid
> +	if (!rec->no_buildid
>  	    && !perf_header__has_feat(&session->header, HEADER_BUILD_ID)) {
> -		pr_err("Couldn't generating buildids. "
> +		pr_err("Couldn't generate buildids. "
>  		       "Use --no-buildid to profile anyway.\n");

After this fix it might make sense to do a s/no_buildid/build_id 
across the source and negate all the conditions. Generally it's 
cleaner to have no negation in structure field names, it avoids 
such double and triple negation problems.

The feature bit did it correctly: it has HEADER_BUILD_ID which 
signals the presence of build-ids.

( Btw., in error messages it might make sense to do a 
  subsystem-wide s/buildid/build-id rename as well, to make it 
  all easier to read - when I read 'buildid' I often keep 
  wondering who that Buil guy is and what he did. )

Thanks,

	Ingo

  reply	other threads:[~2012-02-07  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 22:27 [PATCH] perf-record: no build id option fails David Ahern
2012-02-07  9:06 ` Ingo Molnar [this message]
2012-02-07 14:50   ` Arnaldo Carvalho de Melo
2012-02-17  9:43 ` [tip:perf/core] perf record: No " tip-bot for David Ahern
2012-03-05  8:37 ` tip-bot for David Ahern

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=20120207090622.GC15359@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox