From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>
Subject: [PATCH 0/4] perf tools: libperf related fixes
Date: Sun, 1 Sep 2019 14:48:18 +0200 [thread overview]
Message-ID: <20190901124822.10132-1-jolsa@kernel.org> (raw)
hi,
sending some libperf related fixes.
thanks,
jirka
---
Jiri Olsa (4):
perf tools: Fix python/perf.so compilation
perf tests: Fix static build test
perf tests: Add libperf automated test
libperf: Add missing event.h into install rule
tools/perf/Makefile.perf | 2 +-
tools/perf/lib/Makefile | 1 +
tools/perf/tests/make | 8 ++++++--
3 files changed, 8 insertions(+), 3 deletions(-)
next reply other threads:[~2019-09-01 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 12:48 Jiri Olsa [this message]
2019-09-01 12:48 ` [PATCH 1/4] perf tools: Fix python/perf.so compilation Jiri Olsa
2019-09-01 15:14 ` Arnaldo Carvalho de Melo
2019-09-20 16:21 ` [tip: perf/urgent] perf python: Add missing python/perf.so dependency for libperf tip-bot2 for Jiri Olsa
2019-09-01 12:48 ` [PATCH 2/4] perf tests: Fix static build test Jiri Olsa
2019-09-01 15:15 ` Arnaldo Carvalho de Melo
2019-09-01 15:46 ` Jiri Olsa
2019-09-01 12:48 ` [PATCH 3/4] perf tests: Add libperf automated test Jiri Olsa
2019-09-01 15:18 ` Arnaldo Carvalho de Melo
2019-09-20 16:21 ` [tip: perf/urgent] perf tests: Add libperf automated test for 'make -C tools/perf build-test' tip-bot2 for Jiri Olsa
2019-09-01 12:48 ` [PATCH 4/4] libperf: Add missing event.h into install rule Jiri Olsa
2019-09-01 15:18 ` Arnaldo Carvalho de Melo
2019-09-20 16:21 ` [tip: perf/urgent] libperf: Add missing event.h file to " tip-bot2 for 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=20190901124822.10132-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@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 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.