All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	Ingo Molnar <mingo@kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michael Ellerman <michael@ellerman.id.au>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [V5 0/4] perf: New conditional branch filter
Date: Mon, 07 Apr 2014 13:50:26 +0530	[thread overview]
Message-ID: <53425FCA.40108@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140325161644.GC15074@tassilo.jf.intel.com>

On 03/25/2014 09:46 PM, Andi Kleen wrote:
>> Hey Arnaldo,
>>
>> Do you have any comments or suggestions on this ? Have not received any
>> response on these proposed patch series yet. Thank you.
> 
> I read it earlier and it looks good to me.

Hey Andi,

Can I add your "Reviewed-by" or "Acked-by" to all these four patches ?


  reply	other threads:[~2014-04-07  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  9:06 [V5 0/4] perf: New conditional branch filter Anshuman Khandual
2014-03-07  9:06 ` [V5 1/4] perf: Add PERF_SAMPLE_BRANCH_COND Anshuman Khandual
2014-03-07  9:06 ` [V5 2/4] perf, tool: Conditional branch filter 'cond' added to perf record Anshuman Khandual
2014-03-07  9:06 ` [V5 3/4] x86, perf: Add conditional branch filtering support Anshuman Khandual
2014-03-07  9:06 ` [V5 4/4] perf, documentation: Description for conditional branch filter Anshuman Khandual
2014-03-25 14:52 ` [V5 0/4] perf: New " Anshuman Khandual
2014-03-25 16:16   ` Andi Kleen
2014-04-07  8:20     ` Anshuman Khandual [this message]
2014-04-07 12:18       ` Andi Kleen
2014-03-25 20:16   ` Andi Kleen

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=53425FCA.40108@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=ak@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=mingo@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 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.