From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>, David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@gmail.com>,
Jean Pihet <jean.pihet@linaro.org>
Subject: Re: [PATCH] perf tool: Carve out ctype.h et al
Date: Thu, 26 Jun 2014 09:38:02 +0200 [thread overview]
Message-ID: <20140626073802.GC1177@krava.brq.redhat.com> (raw)
In-Reply-To: <20140625211757.GD18773@kernel.org>
On Wed, Jun 25, 2014 at 06:17:57PM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> >
> > Merge remote-tracking branch 'jolsa/perf/urgent' into ptool-v0.5
> >
> > commit a93f0e551af9e194db38bfe16001e17a3a1d189a
> > Author: Simon Que <sque@chromium.org>
> > Date: Mon Jun 16 11:32:09 2014 -0700
> >
> > perf symbols: Get kernel start address by symbol name
> >
> > by checking out acme/perf/core first.
> >
> > So, guys, can we agree on a common branch to apply patches ontop please?
>
> I'd say work on tip/perf/core, if it doesn't apply on mine or jolsa's,
> we'll fix it up, right Jiri?
yep, tip/perf/core maybe plus merges from acme/perf/core and jolsa/perf/core
should do it ;-)
jirka
next prev parent reply other threads:[~2014-06-26 7:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 9:23 [PATCH] perf tool: Carve out ctype.h et al Borislav Petkov
2014-06-25 19:25 ` Jiri Olsa
2014-06-25 19:42 ` Arnaldo Carvalho de Melo
2014-06-25 20:11 ` Borislav Petkov
2014-06-26 7:36 ` Jiri Olsa
2014-06-26 9:51 ` Borislav Petkov
2014-06-25 20:38 ` Borislav Petkov
2014-06-25 21:17 ` Arnaldo Carvalho de Melo
2014-06-25 21:21 ` Borislav Petkov
2014-06-26 7:38 ` Jiri Olsa [this message]
2014-06-26 10:32 ` Borislav Petkov
2014-06-26 12:14 ` Jiri Olsa
2014-06-27 23:28 ` Borislav Petkov
2014-07-07 20:47 ` Arnaldo Carvalho de Melo
2014-07-07 20:59 ` Borislav Petkov
2014-07-07 21:07 ` Jiri Olsa
2014-07-07 21:27 ` Borislav Petkov
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=20140626073802.GC1177@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=jean.pihet@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=peterz@infradead.org \
--cc=rric@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