From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Yordan Karadzhov <y.karadz@gmail.com>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Subject: Re: [RFC][PATCH 00/24] tools lib traceevent: Rename pevent to tep for preparation for library
Date: Fri, 10 Aug 2018 09:00:10 -0400 [thread overview]
Message-ID: <20180810090010.4537e14a@gandalf.local.home> (raw)
In-Reply-To: <20180810092137.GB14485@krava>
On Fri, 10 Aug 2018 11:21:37 +0200
Jiri Olsa <jolsa@redhat.com> wrote:
> > This is not complete. It is only one of many preparations to make
> > libtraceevent into a legitimate library. There's other naming conventions
> > that will be made. But for now, I would like to hear thoughts about
> > this change before we proceed further.
>
> right, I can see more things that needs rename, like in print_arg*,
> trace_* stuff and others
We are working on renaming the other data structures. As for the
"trace_" it is really "trace_seq_*" That's not going to get renamed. We
may move it to another header file. It matches the trace_seq_* code in
the kernel, and I would like to keep that the same.
>
> I'm also getting weird make error when compiling in libtraceevent dir:
>
> [jolsa@krava traceevent]$ make
> GEN libtraceevent-dynamic-list
> Either missing one of [ plugin_jbd2.so plugin_hrtimer.so plugin_kmem.so plugin_kvm.so plugin_mac80211.so plugin_sched_switch.so plugin_function.so plugin_xen.so plugin_scsi.so plugin_cfg80211.so] or bad version of nm
>
> but that seems to be there even without your patchset,
> so probably something we should look into
Hmm, OK, I'll try to look into that later.
>
> other than that it looks ok to me
Great!
>
> once this is done, we can move forward to put this
> to kernel-tools-libs-devel rpm
For this patch series, do you want to take the patch set, or just pull
from my branch?
-- Steve
next prev parent reply other threads:[~2018-08-10 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 15:55 [RFC][PATCH 00/24] tools lib traceevent: Rename pevent to tep for preparation for library Steven Rostedt
2018-08-08 17:52 ` Steven Rostedt
2018-08-09 8:12 ` Jiri Olsa
2018-08-09 13:40 ` Steven Rostedt
2018-08-10 9:21 ` Jiri Olsa
2018-08-10 13:00 ` Steven Rostedt [this message]
2018-08-10 13:14 ` Jiri Olsa
2018-08-10 16:57 ` Arnaldo Carvalho de Melo
2018-08-15 2:54 ` Steven Rostedt
2018-08-15 7:04 ` Jiri Olsa
2018-08-15 13:54 ` Steven Rostedt
2018-08-15 14:51 ` 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=20180810090010.4537e14a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@gmail.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;
as well as URLs for NNTP newsgroup(s).