linux-kernel - Re: [RFC PATCHSET 0/3] tools lib traceevent: Generic error handling for pevent

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Jun 2012 11:57:49 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC PATCHSET 0/3] tools lib traceevent: Generic error handling for pevent

Hi,

On Tue, 12 Jun 2012 13:49:46 -0400, Steven Rostedt wrote:
> On Tue, 2012-06-12 at 16:42 +0900, Namhyung Kim wrote:
>
>> I don't like the name 'pevent' but since it's a part of the API
>> so I used it for the name.
>> 
>
> Have a better suggestion? It's still a rather new API. We can still
> change trace-cmd and power-top if we can come up with a better naming
> convention.
>
> Speak now or forever hold your piece ;-) (or is that peace?)
>

I don't think I have a good naming sense. :/

As the library name changed, 'tevent' might look like little bit better,
but I'm not sure it's worth changing. How about 'libte', 'lte', or
'lkte' for linux (kernel) trace event? For the last case, 'telk' (trace
event for linux kernel) might be a better name to pronounce.

Any better suggestions?

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/