[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YSQ.7.76.1803151450260.28583@knanqh.ubzr>
Date: Thu, 15 Mar 2018 14:59:32 -0400 (EDT)
From: Nicolas Pitre <nicolas.pitre@...aro.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Jarod Wilson <jarod@...hat.com>,
Prarit Bhargava <prarit@...hat.com>,
Michal Marek <michal.lkml@...kovi.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/7] kbuild: move include/config/ksym/* to
include/ksym/*
On Thu, 15 Mar 2018, Masahiro Yamada wrote:
> 2018-03-15 3:47 GMT+09:00 Nicolas Pitre <nicolas.pitre@...aro.org>:
> > On Thu, 15 Mar 2018, Masahiro Yamada wrote:
> >
> >> The idea of using fixdep was inspired by Kconfig, but autoksyms
> >> is unrelated to Kconfig. So, I want to get those touched files
> >> out of include/config/. The directory include/ksym/ is removed
> >> by "make clean". We do not need to keep it for external module
> >> building.
> >
> > It could be argued that include/config/ is not strictly containing
> > configuration data either and is slightly misleading.
>
> But, slightly related to configuration, IMHO.
> At least they carry timestamps that are updated
> when kernel configuration is changed.
Yes. But for the sake of argument, the ksym timestamps are updated only
when configuration is changed too. Fundamentally they're both about
dependencies, hence my naming suggestion of deps/config/ and deps/ksym/
so not to clutter the top include directory too much.
> The difference between include/config/ and include/ksym/ is that
> files under include/config/ are necessary for building
> external modules (so should be cleaned away by mrproper)
> whereas include/ksym/ is unnecessary for external modules
> since vmlinux and in-kernel modules do not depend on
> external modules.
Agreed.
> I wonder if trimming symbols makes sense for external modules.
Probably not.
Nicolas
Powered by blists - more mailing lists