From: Jiri Olsa <jolsa@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC 0/4] tools lib traceevent: Install fixes
Date: Fri, 19 Jan 2018 16:15:02 +0100 [thread overview]
Message-ID: <20180119151502.GB13089@krava> (raw)
In-Reply-To: <20180119100728.78ae773f@gandalf.local.home>
On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote:
> On Fri, 19 Jan 2018 11:37:13 +0100
> Jiri Olsa <jolsa@redhat.com> wrote:
>
> > hi,
> > I checked on this one and was surprised last email is from 2016 ;-)
> > so we did not move much with this.. is there still will to do that?
> >
> > I think we were kind of waiting for the namespace changes in
> > traceevent library.. like to have some common prefix for public
> > functions/struct, like 'traceevent_' ?
> >
> > thoughts? thanks,
>
> Yes, actually this is back on my radar. I now have full time staff
> working on trace-cmd and kernelshark. One of the up coming changes is
> to start pushing libtraceevent as a real library which means changing
> this.
>
> Thus, do we think "traceevent_" is the proper naming? Could we shorten
> it to "tevent_"? Need to get this bike-shedding exercise out of the way
> first ;-)
tevent is ok with me.. one character far from the current one ;-)
jirka
next prev parent reply other threads:[~2018-01-19 15:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 17:41 [RFC 0/4] tools lib traceevent: Install fixes Jiri Olsa
2016-08-01 17:41 ` [PATCH 1/4] tools lib traceevent: Add install_headers target Jiri Olsa
2016-08-02 2:19 ` Namhyung Kim
2016-08-02 9:30 ` Jiri Olsa
2016-08-01 17:41 ` [PATCH 2/4] tools lib traceevent: Add do_install_mkdir Makefile function Jiri Olsa
2016-08-01 17:41 ` [PATCH 3/4] tools lib traceevent: Rename LIB_FILE to LIB_TARGET Jiri Olsa
2016-08-01 17:41 ` [PATCH 4/4] tools lib traceevent: Add version for traceevent shared object Jiri Olsa
2016-08-02 3:10 ` [RFC 0/4] tools lib traceevent: Install fixes Namhyung Kim
2016-08-02 5:01 ` [PATCH 1/2] tools lib traceevent: Ignore generated library files Namhyung Kim
2016-08-02 5:01 ` [PATCH 2/2] tools lib traceevent: Add str_error_r() Namhyung Kim
2016-08-02 14:27 ` Namhyung Kim
2016-08-04 9:10 ` [tip:perf/urgent] tools lib traceevent: Ignore generated library files tip-bot for Namhyung Kim
2016-08-02 9:31 ` [RFC 0/4] tools lib traceevent: Install fixes Jiri Olsa
2016-08-02 13:48 ` Steven Rostedt
2016-08-02 14:01 ` Jiri Olsa
2016-08-02 14:14 ` Namhyung Kim
2016-08-02 14:18 ` Arnaldo Carvalho de Melo
2016-08-02 14:16 ` Steven Rostedt
2016-08-05 14:13 ` Steven Rostedt
2016-08-05 14:42 ` Arnaldo Carvalho de Melo
2016-08-07 12:56 ` Jiri Olsa
2018-01-19 10:37 ` Jiri Olsa
2018-01-19 15:07 ` Steven Rostedt
2018-01-19 15:15 ` Jiri Olsa [this message]
2018-01-26 6:04 ` Namhyung Kim
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=20180119151502.GB13089@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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 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).