stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: stable@vger.kernel.org
Cc: Changbin Du <changbin.du@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	mhiramat@kernel.org
Subject: [PATCH for 4.9 0/4] tools/perf: Backport fixes for 4.9 for newer toolchain
Date: Tue, 30 Jun 2020 23:45:30 +0900	[thread overview]
Message-ID: <159352833055.45385.11124685086393181445.stgit@devnote2> (raw)

Hi,

While porting failed perf-probe fix to 4.9.y (*), I found the perf
command had build errors on Ubuntu 20.04. Fortunately all issues has
been fixed on the upstream. Thus I ported those patches too on 4.9.y.

(*) https://lore.kernel.org/stable/159257562524637@kroah.com/

I think perf tools in other stable branch also has similar issues.

Thank you,

---

Arnaldo Carvalho de Melo (1):
      perf annotate: Use asprintf when formatting objdump command line

Changbin Du (1):
      perf: Make perf able to build with latest libbfd

Jiri Olsa (1):
      perf tools: Fix snprint warnings for gcc 8

Masami Hiramatsu (1):
      perf probe: Fix to check blacklist address correctly


 tools/perf/builtin-script.c    |   24 ++++++++++++------------
 tools/perf/tests/attr.c        |    4 ++--
 tools/perf/tests/pmu.c         |    2 +-
 tools/perf/util/annotate.c     |   17 ++++++++++++-----
 tools/perf/util/cgroup.c       |    2 +-
 tools/perf/util/parse-events.c |    4 ++--
 tools/perf/util/pmu.c          |    2 +-
 tools/perf/util/probe-event.c  |   21 +++++++++++++++------
 tools/perf/util/srcline.c      |   16 +++++++++++++++-
 9 files changed, 61 insertions(+), 31 deletions(-)

--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>

             reply	other threads:[~2020-06-30 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 14:45 Masami Hiramatsu [this message]
2020-06-30 14:45 ` [PATCH for 4.9 1/4] perf probe: Fix to check blacklist address correctly Masami Hiramatsu
2020-06-30 14:45 ` [PATCH for 4.9 2/4] perf annotate: Use asprintf when formatting objdump command line Masami Hiramatsu
2020-06-30 14:45 ` [PATCH for 4.9 3/4] perf tools: Fix snprint warnings for gcc 8 Masami Hiramatsu
2020-06-30 14:46 ` [PATCH for 4.9 4/4] perf: Make perf able to build with latest libbfd Masami Hiramatsu
2020-07-30  7:37 ` [PATCH for 4.9 0/4] tools/perf: Backport fixes for 4.9 for newer toolchain Greg KH

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=159352833055.45385.11124685086393181445.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=acme@redhat.com \
    --cc=changbin.du@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).