From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v1 0/3] perf version: some follow-up updates
Date: Mon, 9 Apr 2018 18:26:46 +0800 [thread overview]
Message-ID: <1523269609-28824-1-git-send-email-yao.jin@linux.intel.com> (raw)
1. Remove -DNO_LIBPERL and use -DHAVE_LIBPERL_SUPPORT in C code.
2. Remove -DNO_LIBPYTHON and use -DHAVE_LIBPYTHON_SUPPORT in C code.
3. Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT.
4. Don't print "libaudit" line if HAVE_SYSCALL_TABLE_SUPPORT is available
and add a line for HAVE_SYSCALL_TABLE_SUPPORT.
Jin Yao (3):
perf script: Use HAVE_LIBXXX_SUPPORT to replace NO_LIBXXX
perf: Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT
perf version: Print status for syscall_table
tools/perf/Makefile.config | 2 +-
tools/perf/builtin-help.c | 2 +-
tools/perf/builtin-script.c | 4 ++--
tools/perf/builtin-version.c | 3 +++
tools/perf/perf.c | 4 ++--
tools/perf/util/generate-cmdlist.sh | 2 +-
tools/perf/util/syscalltbl.c | 6 +++---
tools/perf/util/trace-event-scripting.c | 4 ++--
8 files changed, 15 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2018-04-09 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:26 Jin Yao [this message]
2018-04-09 10:26 ` [PATCH v1 2/3] perf: Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT Jin Yao
2018-04-16 6:45 ` [tip:perf/urgent] perf tools: " tip-bot for Jin Yao
2018-04-09 10:26 ` [PATCH v1 3/3] perf version: Print status for syscall_table Jin Yao
2018-04-16 6:46 ` [tip:perf/urgent] " tip-bot for Jin Yao
2018-04-11 23:24 ` [PATCH v1 0/3] perf version: some follow-up updates Arnaldo Carvalho de Melo
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=1523269609-28824-1-git-send-email-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@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
Powered by JetHome