From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
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>,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf/annotate: Fix branch instruction with multiple operands
Date: Thu, 1 Jun 2017 19:17:03 +0530 [thread overview]
Message-ID: <59301AD7.5090802@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170601130956.GC2899@kernel.org>
Thanks Arnaldo,
On Thursday 01 June 2017 06:39 PM, Arnaldo Carvalho de Melo wrote:
> Humm, authorship info really gests confusing, can't you just have one
> commit log, combining the original one with what you did, and attribute
> the patch to you and have a:
>
> [acme@jouet linux]$ git log | grep -i originally-by: | wc -l
> 58
> [acme@jouet linux]$
>
> Originally-by: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
>
> Ravi?
>
> I'm trying to catch up on my patch queue, so haven't read this
> thoroughly to have an idea if this is fair or OK, can you guys comment
> on it?
Yes, I've tested Kim's patch on powerpc and it works for me.
-Ravi
next prev parent reply other threads:[~2017-06-01 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 5:59 [PATCH] perf/annotate/powerpc: Fix branch instruction with multiple operands 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 [this message]
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
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=59301AD7.5090802@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=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=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 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.