From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S966932AbcHEOmr (ORCPT <rfc822;w@1wt.eu>);
	Fri, 5 Aug 2016 10:42:47 -0400
Received: from mail.kernel.org ([198.145.29.136]:50494 "EHLO mail.kernel.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S966540AbcHEOmq (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 5 Aug 2016 10:42:46 -0400
Date: Fri, 5 Aug 2016 11:42:41 -0300
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
        Jiri Olsa <jolsa@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
Message-ID: <20160805144241.GP14639@kernel.org>
References: <1470073292-18114-1-git-send-email-jolsa@kernel.org>
 <20160802031055.GB25068@danjae.aot.lge.com>
 <20160802093134.GB2036@krava>
 <20160802094823.4a58b42f@gandalf.local.home>
 <20160802140144.GA18401@krava>
 <20160805101352.6bc16cdf@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160805101352.6bc16cdf@gandalf.local.home>
X-Url: http://acmel.wordpress.com
User-Agent: Mutt/1.6.2 (2016-07-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Em Fri, Aug 05, 2016 at 10:13:52AM -0400, Steven Rostedt escreveu:
> On Tue, 2 Aug 2016 16:01:44 +0200
> Jiri Olsa <jolsa@redhat.com> wrote:
> > > BTW, before we start making this ready for their own libraries, I'd
> > > like to make some changes with the naming convention. Mainly with
> > > event_format and format_field.
> > > 
> > > Perhaps we should change them to pevent_event and pevent_field?  
> > 
> > right, it does not have any global prefix for public symbols
> > 
> > I'd actualy expect something like 'traceevent_',
> > but 'pevent' is ok as well I guess
> 
> OK, what's the consensus here? Should we keep "pevent_" or switch to
> the longer "traceevent_"?

traceevent_ matches libtraceevent, so I think would be more obvious the
association of code with the library.

- Arnaldo
 
> I want to make the patch that gets this ready to ship!
> 
> -- Steve