linux-kernel - Re: [RFC 0/4] tools lib traceevent: Install fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 26 Jan 2018 15:04:34 +0900
From:   Namhyung Kim <namhyung@...nel.org>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>, Jiri Olsa <jolsa@...nel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        David Ahern <dsahern@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>, kernel-team@....com
Subject: Re: [RFC 0/4] tools lib traceevent: Install fixes

Hi Jiri and Steve,

On Fri, Jan 19, 2018 at 04:15:02PM +0100, Jiri Olsa wrote:
> 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@...hat.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 ;-)

I'd suggest 'trev'.

Thanks,
Namhyung