mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: Kim Phillips <kim.phillips@arm.com>,
	anton@samba.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, treeze.taeung@gmail.com,
	borntraeger@de.ibm.com, linux-kernel@vger.kernel.org,
	Robin Murphy <robin.murphy@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2] perf/annotate: Fix branch instruction with multiple operands
Date: Thu, 1 Jun 2017 14:50:52 -0300	[thread overview]
Message-ID: <20170601175052.GI2899@kernel.org> (raw)
In-Reply-To: <59302CCF.6000707@linux.vnet.ibm.com>

Em Thu, Jun 01, 2017 at 08:33:43PM +0530, Ravi Bangoria escreveu:
> Hi Kim, Arnaldo,
> 
> On Thursday 01 June 2017 07:59 PM, Kim Phillips wrote:
> > v2: addressing Arnaldo's clean-this-up comment:  merged commit texts
> > between Ravi's original, author changed in lieu of adding something I
> > hadn't known nor thought about possibly doing: Originally-by: Ravi.
> > Ravi, if that's not OK, provide an alternative means of keeping things
> > clean for Arnaldo, thanks.
> 
> I'm fine :) No issues.

Thanks, applied to perf/urgent.

- Arnaldo

  parent reply	other threads:[~2017-06-01 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  5:59 [PATCH] perf/annotate/powerpc: " Ravi Bangoria
2017-05-26 23:23 ` [PATCH] perf/annotate: " Kim Phillips
2017-06-01 13:09   ` Arnaldo Carvalho de Melo
2017-06-01 13:47     ` Ravi Bangoria
2017-06-01 14:29     ` [PATCH v2] " Kim Phillips
2017-06-01 15:03       ` Ravi Bangoria
2017-06-01 16:42         ` Arnaldo Carvalho de Melo
2017-06-01 17:50         ` Arnaldo Carvalho de Melo [this message]
2017-06-07 15:57       ` [tip:perf/urgent] perf annotate: " tip-bot for Kim Phillips

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=20170601175052.GI2899@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anton@samba.org \
    --cc=borntraeger@de.ibm.com \
    --cc=kim.phillips@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    --cc=robin.murphy@arm.com \
    --cc=treeze.taeung@gmail.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

Powered by JetHome