From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
namhyung@kernel.org, irogers@google.com, songliubraving@fb.com,
yao.jin@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] perf annotate: Misc fixes / improvements
Date: Thu, 27 Feb 2020 11:11:10 -0300 [thread overview]
Message-ID: <20200227141110.GF10761@kernel.org> (raw)
In-Reply-To: <20200206190412.GD1669706@krava>
Em Thu, Feb 06, 2020 at 08:04:12PM +0100, Jiri Olsa escreveu:
> On Tue, Feb 04, 2020 at 10:22:27AM +0530, Ravi Bangoria wrote:
> > Few fixes / improvements related to perf annotate.
> >
> > v2: https://lore.kernel.org/r/20200124080432.8065-1-ravi.bangoria@linux.ibm.com
> >
> > v2->v3:
> > - [PATCH v3 2/6] New function annotation_line__exit() to clear
> > annotation_line objects.
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Thanks applied the series to perf/urgent as it contains a fix.
- Arnaldo
> thanks,
> jirka
>
> >
> > v1: http://lore.kernel.org/r/20200117092612.30874-1-ravi.bangoria@linux.ibm.com
> >
> > v1->v2:
> > - Split [PATCH v1 1/3] into two patches.
> > - Patch 5 and patch 6 are new.
> >
> > Ravi Bangoria (6):
> > perf annotate: Remove privsize from symbol__annotate() args
> > perf annotate: Simplify disasm_line allocation and freeing code
> > perf annotate: Align struct annotate_args
> > perf annotate: Fix segfault with source toggle
> > perf annotate: Make few functions static
> > perf annotate: Get rid of annotation->nr_jumps
> >
> > tools/perf/builtin-top.c | 2 +-
> > tools/perf/ui/gtk/annotate.c | 2 +-
> > tools/perf/util/annotate.c | 115 ++++++++++++++---------------------
> > tools/perf/util/annotate.h | 8 +--
> > 4 files changed, 49 insertions(+), 78 deletions(-)
> >
> > --
> > 2.24.1
> >
>
--
- Arnaldo
next prev parent reply other threads:[~2020-02-27 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:52 [PATCH v3 0/6] perf annotate: Misc fixes / improvements Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 1/6] perf annotate: Remove privsize from symbol__annotate() args Ravi Bangoria
2020-02-29 9:16 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 2/6] perf annotate: Simplify disasm_line allocation and freeing code Ravi Bangoria
2020-02-29 9:16 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 3/6] perf annotate: Align struct annotate_args Ravi Bangoria
2020-02-29 9:16 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 4/6] perf annotate: Fix segfault with source toggle Ravi Bangoria
2020-02-29 9:16 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 5/6] perf annotate: Make few functions static Ravi Bangoria
2020-02-04 4:52 ` [PATCH v3 6/6] perf annotate: Get rid of annotation->nr_jumps Ravi Bangoria
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Ravi Bangoria
2020-02-06 19:04 ` [PATCH v3 0/6] perf annotate: Misc fixes / improvements Jiri Olsa
2020-02-27 14:11 ` Arnaldo Carvalho de Melo [this message]
2020-02-28 14:42 ` Ravi Bangoria
2020-02-28 14:59 ` Arnaldo Melo
2020-02-28 15:01 ` Arnaldo Melo
2020-02-10 12:18 ` Jiri Olsa
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=20200227141110.GF10761@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox