From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com
Subject: Re: [PATCH 0/6] Show branch flags/cycles in perf report --branch-history callgraph view
Date: Wed, 19 Oct 2016 10:55:34 +0200 [thread overview]
Message-ID: <20161019085534.GA3041@krava> (raw)
In-Reply-To: <6cf023b5-0059-5010-9998-4ef534fde399@linux.intel.com>
On Wed, Oct 19, 2016 at 04:46:02PM +0800, Jin, Yao wrote:
> It's based on the current branch "remotes/origin/perf/core" of tip
> (https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git).
>
> Should the patch be based on the branch "remotes/origin/perf/core" of the
> repo (https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git)?
yep, that's what we do normaly.. because Arnaldo has already
some other new patches pilled up
thanks,
jirka
next prev parent reply other threads:[~2016-10-19 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 9:25 [PATCH 0/6] Show branch flags/cycles in perf report --branch-history callgraph view Jin Yao
2016-10-19 8:26 ` Jiri Olsa
2016-10-19 8:46 ` Jin, Yao
2016-10-19 8:55 ` Jiri Olsa [this message]
2016-10-19 13:11 ` Arnaldo Carvalho de Melo
2016-10-19 9:25 ` [PATCH 1/6] perf report: Add branch flag to callchain cursor node Jin Yao
2016-10-19 9:25 ` [PATCH 2/6] perf report: Caculate and return the branch counting in callchain Jin Yao
2016-10-19 9:25 ` [PATCH 3/6] perf report: Create a symbol_conf flag for showing branch flag counting Jin Yao
2016-10-19 9:25 ` [PATCH 4/6] perf report: Show branch info in callchain entry with stdio mode Jin Yao
2016-10-19 9:25 ` [PATCH 5/6] perf report: Show branch info in callchain entry with browser mode Jin Yao
2016-10-19 9:25 ` [PATCH 6/6] perf report: Display keys Predicted/Abort/Cycles in --branch-history Jin Yao
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=20161019085534.GA3041@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=yao.jin@linux.intel.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