From: Taeung Song <taeung.dev@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Wang Nan <wangnan0@huawei.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v8 2/5] perf config: Bring declarations about config from util/cache.h to util/config.h
Date: Sun, 12 Jun 2016 15:28:55 +0900 [thread overview]
Message-ID: <575D0127.30008@gmail.com> (raw)
In-Reply-To: <575B6262.6030607@gmail.com>
Hi,
I have a question about header files.
I'm cleaning up source files that used cache.h
after moving codes about config from cache.h to config.h.
But I found there are header files that are repeatedly declared over all.
For example, builtin-report.c include util/sort.h,
perf.h, util/util.h, util/cache.h and etc.
However, util/sort.h also have #include "cache.h"
and cache.h even include util.h and perf.h.
Isn't this a problem (but this is minor) ?
Of course, this patch don't need to contain codes
to fix this above problem.
Should we fix this problem ?
(If we do, I'd individually send patches for this problem.)
Thanks,
Taeung
On 06/11/2016 09:59 AM, Taeung Song wrote:
> Good evening :)
>
> On 06/11/2016 04:06 AM, Arnaldo Carvalho de Melo wrote:
>> Em Fri, Jun 10, 2016 at 03:20:43PM +0900, Taeung Song escreveu:
>>> On 06/09/2016 10:29 PM, Arnaldo Carvalho de Melo wrote:
>>>>> +++ b/tools/perf/util/cache.h
>>>>> @@ -7,6 +7,7 @@
>>>>> #include <subcmd/pager.h>
>>>>> +#include "config.h"
>>
>>>> Why have you added that? Are those config functions used in cache.h?
>>
>>> Yes, it does. Many source files include cache.h
>>> e.g. builtin-annoate.c, util/color.c, builtin-report.c and etc.
>>> And They can use perf_config() function including this header file.
>>
>>> So, If I totally eliminate not only declarations about config
>>> but also #include "util/config.h" at util/cache.h,
>>> we should add '#include "util/config.h"' to each source file that
>>> need perf_config() overall.
>>
>> Sure, that is how we should do it. We should not include cache.h just to
>> get what is in config.h, we should instead include config.h.
>>
>> This way when we do a change to cache.h we will not be rebuilding all
>> those files that depend on it just to get config.h.
>>
>> What you're doing, removing from cache.h things that shouldn't be there
>> in the first place is good, among other things, because of that.
>>
>
> Granted!
> I've also experienced the situation all those files which include cache.h
> are rebuilt after I changed cache.h.
> It also seems a problem as you mention.
>
> So, I'll send this patch that reflect what you said with v9.
>
> Have a nice weekend :-D
>
> Thanks,
> Taeung
next prev parent reply other threads:[~2016-06-12 6:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 12:36 [RFC][PATCH v8 0/5] perf config: Reimplement perf_config() using perf_config_set__inter() Taeung Song
2016-06-08 12:36 ` [BUGFIX][PATCH v8 1/5] perf config: Handle the error about NULL at perf_config_set__delete() Taeung Song
2016-06-16 8:31 ` [tip:perf/core] perf config: Handle " tip-bot for Taeung Song
2016-06-08 12:36 ` [PATCH v8 2/5] perf config: Bring declarations about config from util/cache.h to util/config.h Taeung Song
2016-06-09 13:29 ` Arnaldo Carvalho de Melo
2016-06-10 6:20 ` Taeung Song
2016-06-10 19:06 ` Arnaldo Carvalho de Melo
2016-06-11 0:59 ` Taeung Song
2016-06-12 6:28 ` Taeung Song [this message]
2016-06-08 12:36 ` [PATCH v8 3/5] perf config: Reimplement perf_config() using perf_config_set__iter() Taeung Song
2016-06-09 13:34 ` Arnaldo Carvalho de Melo
2016-06-10 10:58 ` Taeung Song
2016-06-12 8:57 ` Taeung Song
2016-06-20 10:00 ` [PATCH v8 3/5] perf config: Reimplement perf_config() using perf_config_set__it to Taeung Song
2016-06-09 13:41 ` [PATCH v8 3/5] perf config: Reimplement perf_config() using perf_config_set__iter() Arnaldo Carvalho de Melo
2016-06-10 11:05 ` Taeung Song
2016-06-08 12:36 ` [PATCH v8 4/5] perf config: Use zfree() instead of free() at perf_config_set__delete() Taeung Song
2016-06-09 13:37 ` Arnaldo Carvalho de Melo
2016-06-10 11:03 ` Taeung Song
2016-06-08 12:36 ` [PATCH v8 5/5] perf config: Reimplement show_config() using perf_config_set__iter() 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=575D0127.30008@gmail.com \
--to=taeung.dev@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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).