From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-devel@vger.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 13:57:06 -0300 [thread overview]
Message-ID: <20180810165706.GH5395@kernel.org> (raw)
In-Reply-To: <20180810131401.GB4162@krava>
Em Fri, Aug 10, 2018 at 03:14:01PM +0200, Jiri Olsa escreveu:
> On Fri, Aug 10, 2018 at 09:00:10AM -0400, Steven Rostedt wrote:
> > 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?
>
> Arnaldo takes care of that, but I guess pulling from branch is the prefered way
I'll try pulling and building it automatically patch by patch,
- Arnaldo
next prev parent reply other threads:[~2018-08-10 19:27 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
2018-08-10 13:14 ` Jiri Olsa
2018-08-10 16:57 ` Arnaldo Carvalho de Melo [this message]
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=20180810165706.GH5395@kernel.org \
--to=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=rostedt@goodmis.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).