[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160304135848.GA15486@danjae.kornet>
Date: Fri, 4 Mar 2016 22:58:48 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Taeung Song <treeze.taeung@...il.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Jiri Olsa <jolsa@...hat.com>,
perf group <linux-perf-users@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v11 17/24] perf config: Collect configs to handle config
variables
Hi Taeung,
On Fri, Mar 04, 2016 at 09:45:44PM +0900, Taeung Song wrote:
> Hi, Namhyung and all
>
> (I'm modifying this patch to be tidy)
> I have a mere question about name of a variable for
> current config list that contains section list which has key-value
> pairs from ~/.perfconfig or $(sysconfdir)/perfconfig config file.
>
> (This variable is designed to be used by several functions
> that handle config information(key-value pairs).)
>
> I used 'sections' for this variable (type is 'struct list_head'),
> but IMHO, I think that renaming it is better e.g.
>
> 1) 'cfglist'
> 2) 'configlist'
> 3) 'config_list'
> 4) 'cfgset'
> 5) 'configset'
> 6) 'config_set'
> ... :-\
>
> It is trivial question,
> but I wanna know a opinion of other people. :-)
I'd go with 3 or 6. Or simply 'configs' or 'perf_configs' is fine for
me.
Thanks,
Namhyung
Powered by blists - more mailing lists