Commit f276031b authored by Masahiro Yamada's avatar Masahiro Yamada

kheaders: explain why include/config/autoconf.h is excluded from md5sum

This comment block explains why include/generated/compile.h is omitted,
but nothing about include/generated/autoconf.h, which might be more
difficult to understand. Add more comments.
Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
parent 1463f74f
...@@ -32,8 +32,15 @@ fi ...@@ -32,8 +32,15 @@ fi
all_dirs="$all_dirs $dir_list" all_dirs="$all_dirs $dir_list"
# include/generated/compile.h is ignored because it is touched even when none # include/generated/compile.h is ignored because it is touched even when none
# of the source files changed. This causes pointless regeneration, so let us # of the source files changed.
# ignore them for md5 calculation. #
# When Kconfig regenerates include/generated/autoconf.h, its timestamp is
# updated, but the contents might be still the same. When any CONFIG option is
# changed, Kconfig touches the corresponding timestamp file include/config/*.h.
# Hence, the md5sum detects the configuration change anyway. We do not need to
# check include/generated/autoconf.h explicitly.
#
# Ignore them for md5 calculation to avoid pointless regeneration.
headers_md5="$(find $all_dirs -name "*.h" | headers_md5="$(find $all_dirs -name "*.h" |
grep -v "include/generated/compile.h" | grep -v "include/generated/compile.h" |
grep -v "include/generated/autoconf.h" | grep -v "include/generated/autoconf.h" |
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment