linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf trace: Make command line arguments consistent with perf-record
Date: Tue, 20 Aug 2013 14:11:18 -0300	[thread overview]
Message-ID: <20130820171118.GE8488@ghostprotocols.net> (raw)
In-Reply-To: <521397DE.5010306@gmail.com>

Em Tue, Aug 20, 2013 at 10:22:54AM -0600, David Ahern escreveu:
> On 8/20/13 8:51 AM, Arnaldo Carvalho de Melo wrote:
> >Em Tue, Aug 20, 2013 at 08:47:56AM -0600, David Ahern escreveu:
> >>Common arguments like thread id, CPU list, mmap pages, etc should be
> >>consistent across perf commands.

> >>Signed-off-by: David Ahern <dsahern@gmail.com>
> >>  tools/perf/builtin-trace.c |   12 ++++++------

> >  tools/perf/Documentation/perf-trace.txt part missing :-)

> grrrr... Added a check in the git pre-commit hook to remind me:
> 
> $ git commit -a
> changing command line arguments. Did you update the man page?

Hey, post it somewhere, please! I'd like to use it too. :-)
 
> Will resend later today.
> David

  reply	other threads:[~2013-08-20 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 14:47 [PATCH] perf trace: Make command line arguments consistent with perf-record David Ahern
2013-08-20 14:51 ` Arnaldo Carvalho de Melo
2013-08-20 16:22   ` David Ahern
2013-08-20 17:11     ` Arnaldo Carvalho de Melo [this message]
2013-08-20 17:19       ` David Ahern
  -- strict thread matches above, loose matches on Subject: below --
2013-08-19 17:04 David Ahern
2013-08-19 19:06 ` Arnaldo Carvalho de Melo
2013-08-20 14:19   ` David Ahern
2013-08-20 14:43     ` Arnaldo Carvalho de Melo

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=20130820171118.GE8488@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).