diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-07-17 08:17:49 +0200 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-07-17 15:39:27 +0200 |
commit | 7e13191879d6d589cd987a8db3a70019251fc757 (patch) | |
tree | bb7f7e187bc33cdee33c2518321aeb98cc8a328b /scripts/modules-check.sh | |
parent | coccinelle: api: add devm_platform_ioremap_resource script (diff) | |
download | linux-7e13191879d6d589cd987a8db3a70019251fc757.tar.xz linux-7e13191879d6d589cd987a8db3a70019251fc757.zip |
kbuild: do not create empty modules.order in the prepare stage
Currently, $(objtree)/modules.order is touched in two places.
In the 'prepare0' rule, scripts/Makefile.build creates an empty
modules.order while processing 'obj=.'
In the 'modules' rule, the top-level Makefile overwrites it with
the correct list of modules.
While this might be a good side-effect that modules.order is made
empty every time (probably this is not intended functionality),
I personally do not like this behavior.
Create modules.order only when it is sensible to do so.
This avoids creating the following pointless files:
scripts/basic/modules.order
scripts/dtc/modules.order
scripts/gcc-plugins/modules.order
scripts/genksyms/modules.order
scripts/mod/modules.order
scripts/modules.order
scripts/selinux/genheaders/modules.order
scripts/selinux/mdp/modules.order
scripts/selinux/modules.order
Going forward, $(objtree)/modules.order lists the modules that
was built in the last successful build.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'scripts/modules-check.sh')
0 files changed, 0 insertions, 0 deletions