public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: David Ahern <dsahern@gmail.com>,
	acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
	namhyung@kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mike Galbraith <efault@gmx.de>, Jiri Olsa <jolsa@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH 2/2] perf sched: Add documentation for timehist options
Date: Mon, 2 Dec 2013 13:38:08 +0100	[thread overview]
Message-ID: <20131202123808.GA22212@gmail.com> (raw)
In-Reply-To: <20131202060729.GA28684@linux.vnet.ibm.com>


* Srikar Dronamraju <srikar@linux.vnet.ibm.com> wrote:

> * David Ahern <dsahern@gmail.com> [2013-12-01 17:23:15]:
> 
> > Add entry to perf-sched documentation for timehist command and its
> > options.
> > 
> > v2: Addressed comments by Namhyung
> > 
> > Signed-off-by: David Ahern <dsahern@gmail.com>
> > Cc: Ingo Molnar <mingo@kernel.org>
> > Cc: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Mike Galbraith <efault@gmx.de>
> > Cc: Jiri Olsa <jolsa@redhat.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: Stephane Eranian <eranian@google.com>
> > Cc: Pekka Enberg <penberg@kernel.org>
> > ---
> >  tools/perf/Documentation/perf-sched.txt | 61 ++++++++++++++++++++++++++++++++-
> >  1 file changed, 60 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/perf/Documentation/perf-sched.txt b/tools/perf/Documentation/perf-sched.txt
> > index 8ff4df956951..e7bb19fcdbff 100644
> > --- a/tools/perf/Documentation/perf-sched.txt
> > +++ b/tools/perf/Documentation/perf-sched.txt
> > @@ -8,7 +8,7 @@ perf-sched - Tool to trace/measure scheduler properties (latencies)
> >  SYNOPSIS
> >  --------
> >  [verse]
> > -'perf sched' {record|latency|map|replay|script}
> > +'perf sched' {record|latency|map|replay|script|timehist}
> >  
> >  DESCRIPTION
> >  -----------
> > @@ -36,6 +36,11 @@ There are five variants of perf sched:
> 
> Nit: There are six variants now.

Trick: it might make sense to use a more future-proof phrase:

		       There are several variants of perf sched:

;-)

Thanks,

	Ingo

  reply	other threads:[~2013-12-02 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  0:23 [PATCH 0/2] perf: sched timehist command - v2 David Ahern
2013-12-02  0:23 ` [PATCH 1/2] perf sched: Introduce " David Ahern
2013-12-02  7:58   ` Namhyung Kim
2013-12-02 14:28     ` David Ahern
2013-12-02  9:33   ` Pekka Enberg
2013-12-02 14:33     ` David Ahern
2013-12-02 16:19     ` David Ahern
2013-12-02  0:23 ` [PATCH 2/2] perf sched: Add documentation for timehist options David Ahern
2013-12-02  6:07   ` Srikar Dronamraju
2013-12-02 12:38     ` Ingo Molnar [this message]
2013-12-02  7:41   ` Namhyung Kim
2013-12-02 14:37     ` 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=20131202123808.GA22212@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=penberg@kernel.org \
    --cc=srikar@linux.vnet.ibm.com \
    /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