From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Kim Phillips <kim.phillips@arm.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
Anton Blanchard <anton@samba.org>,
Robin Murphy <robin.murphy@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Taeung Song <treeze.taeung@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
perf group <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH v2] perf annotate: fix parsing aarch64 branch instructions after objdump update
Date: Thu, 30 Aug 2018 15:47:06 -0300 [thread overview]
Message-ID: <20180830184706.GH6097@kernel.org> (raw)
In-Reply-To: <20180827125340.a2f7e291901d17cea05daba4@arm.com>
Em Mon, Aug 27, 2018 at 12:53:40PM -0500, Kim Phillips escreveu:
> v2: address acme's comments:
> - consolidate into a validate_comma()
> - call from an additional couple of places necessary
> - don't listen to checkpatch wrt reflowing jump__parse definition
> line to less than 80 characters, just rm the __maybe_unused
> - re-tested no diff on x86_64 and power arch, arm64 conditional
> branches fixed.
Thanks for taking into account my comments, applied.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] perf annotate: fix parsing aarch64 branch instructions after objdump update
Date: Thu, 30 Aug 2018 15:47:06 -0300 [thread overview]
Message-ID: <20180830184706.GH6097@kernel.org> (raw)
In-Reply-To: <20180827125340.a2f7e291901d17cea05daba4@arm.com>
Em Mon, Aug 27, 2018 at 12:53:40PM -0500, Kim Phillips escreveu:
> v2: address acme's comments:
> - consolidate into a validate_comma()
> - call from an additional couple of places necessary
> - don't listen to checkpatch wrt reflowing jump__parse definition
> line to less than 80 characters, just rm the __maybe_unused
> - re-tested no diff on x86_64 and power arch, arm64 conditional
> branches fixed.
Thanks for taking into account my comments, applied.
- Arnaldo
next prev parent reply other threads:[~2018-08-30 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 0:10 [PATCH] perf annotate: fix parsing aarch64 branch instructions after objdump update Kim Phillips
2018-08-24 0:10 ` Kim Phillips
2018-08-24 0:10 ` Kim Phillips
2018-08-24 7:59 ` Thomas-Mich Richter
2018-08-24 7:59 ` Thomas-Mich Richter
2018-08-24 21:45 ` Kim Phillips
2018-08-24 21:45 ` Kim Phillips
2018-08-24 21:45 ` Kim Phillips
2018-08-27 12:50 ` Arnaldo Carvalho de Melo
2018-08-27 12:50 ` Arnaldo Carvalho de Melo
2018-08-27 17:53 ` [PATCH v2] " Kim Phillips
2018-08-27 17:53 ` Kim Phillips
2018-08-30 18:47 ` Arnaldo Carvalho de Melo [this message]
2018-08-30 18:47 ` Arnaldo Carvalho de Melo
2018-09-06 13:07 ` [tip:perf/core] perf annotate: Fix " 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=20180830184706.GH6097@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anton@samba.org \
--cc=borntraeger@de.ibm.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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 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.