linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Taeung Song <treeze.taeung@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	perf group <linux-perf-users@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v11 17/24] perf config: Collect configs to handle config variables
Date: Fri, 4 Mar 2016 22:58:48 +0900	[thread overview]
Message-ID: <20160304135848.GA15486@danjae.kornet> (raw)
In-Reply-To: <56D98378.4080208@gmail.com>

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

  reply	other threads:[~2016-03-04 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447768424-17327-1-git-send-email-treeze.taeung@gmail.com>
     [not found] ` <1447768424-17327-17-git-send-email-treeze.taeung@gmail.com>
     [not found]   ` <20151118051525.GP7062@sejong>
2016-03-04 12:45     ` [PATCH v11 17/24] perf config: Collect configs to handle config variables Taeung Song
2016-03-04 13:58       ` Namhyung Kim [this message]
2016-03-05  2:55         ` Taeung Song

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=20160304135848.GA15486@danjae.kornet \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=treeze.taeung@gmail.com \
    /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).