diff options
author | Daniel Gomez <da.gomez@samsung.com> | 2025-03-28 17:28:37 +0300 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2025-04-06 00:22:01 +0300 |
commit | a26fe287eed112b4e21e854f173c8918a6a8596d (patch) | |
tree | 9bf3434cf1a70d522ed083087c9cfadcef17683d /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
parent | 3b8241f64c469e449e862cf2bdc50b879fa18f93 (diff) | |
download | linux-a26fe287eed112b4e21e854f173c8918a6a8596d.tar.xz |
kconfig: merge_config: use an empty file as initfile
The scripts/kconfig/merge_config.sh script requires an existing
$INITFILE (or the $1 argument) as a base file for merging Kconfig
fragments. However, an empty $INITFILE can serve as an initial starting
point, later referenced by the KCONFIG_ALLCONFIG Makefile variable
if -m is not used. This variable can point to any configuration file
containing preset config symbols (the merged output) as stated in
Documentation/kbuild/kconfig.rst. When -m is used $INITFILE will
contain just the merge output requiring the user to run make (i.e.
KCONFIG_ALLCONFIG=<$INITFILE> make <allnoconfig/alldefconfig> or make
olddefconfig).
Instead of failing when `$INITFILE` is missing, create an empty file and
use it as the starting point for merges.
Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions