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 - v3
Date: Tue, 20 Aug 2013 15:07:49 -0300	[thread overview]
Message-ID: <20130820180749.GF8488@ghostprotocols.net> (raw)
In-Reply-To: <1377018945-21940-1-git-send-email-dsahern@gmail.com>

Em Tue, Aug 20, 2013 at 11:15:45AM -0600, David Ahern escreveu:
> Common arguments like thread id, CPU list, mmap pages, etc should be
> consistent across perf commands.
> 
> v3: Updated man page
> v2: rebased to latest core branch

Thanks, applied.

- Arnaldo

  reply	other threads:[~2013-08-20 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 17:15 [PATCH] perf trace: Make command line arguments consistent with perf-record - v3 David Ahern
2013-08-20 18:07 ` Arnaldo Carvalho de Melo [this message]
2013-08-29 10:08 ` [tip:perf/core] perf trace: Make command line arguments consistent with perf-record 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=20130820180749.GF8488@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).