mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	David Ahern <dsahern@gmail.com>, Don Zickus <dzickus@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
	Namhyung Kim <namhyung@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/2] perf/tests improvements
Date: Fri, 6 Jun 2014 16:51:11 +0200	[thread overview]
Message-ID: <20140606145106.GB8865@krava.brq.redhat.com> (raw)
In-Reply-To: <1402063909-13859-1-git-send-email-acme@kernel.org>

On Fri, Jun 06, 2014 at 11:11:47AM -0300, Arnaldo Carvalho de Melo wrote:
> Hi Jiri,
> 
> 	Experimenting with more topic branches, this time for things you're the
> are the original developer and de facto maintainer, the tools/perf/tests/ harness.
> 
> 	This was done on top of your perf/core branch, please let me know if all is
> ok and then you can try pulling from it or perhaps you could just ack it and then
> Ingo could pull it directly, opinions? Ingo?

either way works for me,

thanks,
jirka

  parent reply	other threads:[~2014-06-06 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 14:11 Arnaldo Carvalho de Melo
2014-06-06 14:11 ` [PATCH 1/2] perf tools: Emit more precise message for missing glibc static library Arnaldo Carvalho de Melo
2014-06-10 15:50   ` Don Zickus
2014-06-10 18:16     ` perf tools: MULTILIB install issues. was " Arnaldo Carvalho de Melo
2014-06-06 14:11 ` [PATCH 2/2] perf tests: Show the inner make output when an error happens Arnaldo Carvalho de Melo
2014-06-06 14:50   ` Jiri Olsa
2014-06-06 15:45     ` Arnaldo Carvalho de Melo
2014-06-06 14:51 ` Jiri Olsa [this message]
2014-06-06 15:06   ` [GIT PULL 0/2] perf/tests improvements 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=20140606145106.GB8865@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®