All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	mpe@ellerman.id.au, Linux-kernel@vger.kernel.org,
	ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v9 0/7] perf report: Show branch type
Date: Mon, 17 Jul 2017 10:19:09 +0200	[thread overview]
Message-ID: <20170717081909.GA29751@krava> (raw)
In-Reply-To: <1500289603-4352-1-git-send-email-yao.jin@linux.intel.com>

On Mon, Jul 17, 2017 at 07:06:36PM +0800, Jin Yao wrote:
> v9:
> ---
>    It only changes the patch "perf/x86/intel: Record branch type".
>    Peter suggests to use __ffs() to find first bit.
>    Yes, with this change, the code is simpler and clearer.
> 
>    No other functional changes.

I think I've already acked this one, anyway for the tools part:

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

  reply	other threads:[~2017-07-17  8:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 11:06 [PATCH v9 0/7] perf report: Show branch type Jin Yao
2017-07-17  8:19 ` Jiri Olsa [this message]
2017-07-17 11:06 ` [PATCH v9 1/7] perf/core: Define the common branch type classification Jin Yao
2017-07-17 11:06 ` [PATCH v9 2/7] perf/x86/intel: Record branch type Jin Yao
2017-07-17  8:11   ` Jiri Olsa
2017-07-17  8:28     ` Jin, Yao
2017-07-18  9:23       ` Peter Zijlstra
2017-07-17 11:06 ` [PATCH v9 3/7] perf record: Create a new option save_type in --branch-filter Jin Yao
2017-07-17 11:06 ` [PATCH v9 4/7] perf report: Refactor the branch info printing code Jin Yao
2017-07-17 11:06 ` [PATCH v9 5/7] perf util: Create branch.c/.h for common branch functions Jin Yao
2017-07-17 11:06 ` [PATCH v9 6/7] perf report: Show branch type statistics for stdio mode Jin Yao
2017-07-17 11:06 ` [PATCH v9 7/7] perf report: Show branch type in callchain entry 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=20170717081909.GA29751@krava \
    --to=jolsa@redhat.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=yao.jin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.