From: Steven Rostedt <rostedt@goodmis.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement
Date: Mon, 23 Sep 2019 11:59:29 -0400 [thread overview]
Message-ID: <20190923115929.453b68f1@oasis.local.home> (raw)
In-Reply-To: <20190923111248.5ebdbfd5@oasis.local.home>
On Mon, 23 Sep 2019 11:12:48 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Yeah. Let's not apply this one yet till we figure out what broke. I'll
> take a look at it too.
Does this help?
-- Steve
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index f9807d8c005b..7544166dd466 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -292,7 +292,7 @@ endif
LIBTRACEEVENT = $(TE_PATH)libtraceevent.a
export LIBTRACEEVENT
-LIBTRACEEVENT_DYNAMIC_LIST = $(TE_PATH)libtraceevent-dynamic-list
+LIBTRACEEVENT_DYNAMIC_LIST = $(TE_PATH)plugins/libtraceevent-dynamic-list
#
# The static build has no dynsym table, so this does not work for
@@ -737,7 +737,7 @@ libtraceevent_plugins: FORCE
$(Q)$(MAKE) -C $(TRACE_EVENT_DIR) $(LIBTRACEEVENT_FLAGS) O=$(OUTPUT) plugins
$(LIBTRACEEVENT_DYNAMIC_LIST): libtraceevent_plugins
- $(Q)$(MAKE) -C $(TRACE_EVENT_DIR) $(LIBTRACEEVENT_FLAGS) O=$(OUTPUT) $(OUTPUT)libtraceevent-dynamic-list
+ $(Q)$(MAKE) -C $(TRACE_EVENT_DIR) $(LIBTRACEEVENT_FLAGS) O=$(OUTPUT) $(OUTPUT)plugins/libtraceevent-dynamic-list
$(LIBTRACEEVENT)-clean:
$(call QUIET_CLEAN, libtraceevent)
next prev parent reply other threads:[~2019-09-23 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 21:23 [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement Steven Rostedt
2019-09-19 21:23 ` [PATCH 1/6] tools/lib/traceevent: Man pages for libtraceevent event print related API Steven Rostedt
2019-09-19 21:23 ` [PATCH 2/6] tools/lib/traceevent: Man pages fix, rename tep_ref_get() to tep_get_ref() Steven Rostedt
2019-09-19 21:23 ` [PATCH 3/6] tools/lib/traceevent: Man pages fix, changes in event printing APIs Steven Rostedt
2019-09-19 21:23 ` [PATCH 4/6] tools/lib/traceevent: Add tep_get_event() in event-parse.h Steven Rostedt
2019-09-19 21:23 ` [PATCH 5/6] tools/lib/traceevent: Man pages for tep plugins APIs Steven Rostedt
2019-09-19 21:23 ` [PATCH 6/6] tools/lib/traceevent: Move traceevent plugins in its own subdirectory Steven Rostedt
2019-09-23 14:28 ` [PATCH 0/6] tools/lib/traceevent: Man page updates and some file movement Arnaldo Carvalho de Melo
2019-09-23 14:39 ` Arnaldo Carvalho de Melo
2019-09-23 14:52 ` Arnaldo Carvalho de Melo
2019-09-23 15:12 ` Steven Rostedt
2019-09-23 15:59 ` Steven Rostedt [this message]
2019-09-23 17:38 ` 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=20190923115929.453b68f1@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mingo@kernel.org \
--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.