author | Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com> | |
Fri, 30 Jan 2015 21:54:32 +0000 (15:54 -0600) | ||
committer | Lokesh Vutla <lokeshvutla@ti.com> | |
Mon, 9 Feb 2015 07:05:03 +0000 (12:35 +0530) | ||
commit | d697eb956a7fb11e467c5dc24e0212db341a926e | |
tree | 5d3563dc3882261ba4c06a942ec796a0b5983f04 | tree | snapshot (tar.xz tar.gz zip) |
parent | ee1a2a09f9c2b634a18cab2d768bb16f1491b9b6 | commit | diff |
ti_config_fragments/baseport.cfg: explicitly enable DEBUG_FS
CONFIG_DEBUG_FS gets automatically selected by CONFIG_TRACING. However,
with CONFIG_FTRACE disabled, CONFIG_DEBUG_FS, DEBUG_FS should have
been removed from the final kernel configuration. It is not the case
since defconfig_merge.sh appends config flags added by config fragments
to the end of the omap2plus based generated config options.
In contrast, tools like merge_config.sh (under scripts/kconfig)
take all config and also account for dependencies. Hence disabling
FTRACE causes DEBUG_FS also to be disabled and therefore enabling
DEBUG_FS explicitly.
Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com>
CONFIG_DEBUG_FS gets automatically selected by CONFIG_TRACING. However,
with CONFIG_FTRACE disabled, CONFIG_DEBUG_FS, DEBUG_FS should have
been removed from the final kernel configuration. It is not the case
since defconfig_merge.sh appends config flags added by config fragments
to the end of the omap2plus based generated config options.
In contrast, tools like merge_config.sh (under scripts/kconfig)
take all config and also account for dependencies. Hence disabling
FTRACE causes DEBUG_FS also to be disabled and therefore enabling
DEBUG_FS explicitly.
Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com>
ti_config_fragments/baseport.cfg | diff | blob | history |