[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160405133819.GB5945@kernel.org>
Date: Tue, 5 Apr 2016 10:38:19 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Taeung Song <taeung.dev@...il.com>
Cc: Vinson Lee <vlee@...edesktop.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Taeung Song <treeze.taeung@...il.com>,
Jiri Olsa <jolsa@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Alexei Starovoitov <ast@...mgrid.com>,
Wang Nan <wangnan0@...wei.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf config: Fix build with older toolchain.
Em Tue, Apr 05, 2016 at 02:24:19PM +0900, Taeung Song escreveu:
> On 04/05/2016 07:07 AM, Vinson Lee wrote:
> > if (!strcmp(var, "buildid.dir")) {
> >- const char *dirname = perf_config_dirname(var, value);
> >+ const char *v = perf_config_dirname(var, value);
>
> Why you use 'v' variable name ?
>
> 'v' variable name was used in set_buildid_dir(), too.
> But I send a patch renaming 'v' to 'home' because 'home' is more readable.
> 37194f4 ("perf config: Rename 'v' to 'home' in set_buildid_dir()")
> https://lkml.org/lkml/2016/3/27/98
>
> IMHO, I like using 'dir' instead of 'v'.
Whatever, I'm switching this to 'dir', but don't pay _that_ much
attention to variables that have such a narrow scope...
- Arnaldo
Powered by blists - more mailing lists