summaryrefslogtreecommitdiff
path: root/drivers/firmware/efi/Kconfig
diff options
context:
space:
mode:
authorUlf Magnusson <ulfalizer@gmail.com>2017-10-09 01:14:48 +0300
committerMasahiro Yamada <yamada.masahiro@socionext.com>2018-01-21 18:49:28 +0300
commitdf60f4b92d3d0b0b91267532ea2584e3b6b58b2f (patch)
treea36d7160de062b7339494d362044d6e208e5c9f8 /drivers/firmware/efi/Kconfig
parent0735f7e5def2ab4158aac8d35f3661e8819dc232 (diff)
downloadlinux-df60f4b92d3d0b0b91267532ea2584e3b6b58b2f.tar.xz
kconfig: Remove menu_end_entry()
menu_end_entry() is empty and completely unused as far as I can tell: $ git log -G menu_end_entry --oneline a02f057 [PATCH] kconfig: improve error handling in the parser 1da177e Linux-2.6.12-rc2 Last one is the initial Git commit, where menu_end_entry() is empty as well. I couldn't find anything that redefined it on Google either. It might be a debugging helper for setting a breakpoint after each config, menuconfig, and comment is parsed. IMO it hurts more than it helps in that case by making the parsing code look more complicated at a glance than it really is, and I suspect it doesn't get used much. Tested by running the Kconfiglib test suite, which indirectly verifies that the .config files generated by the C implementation for each defconfig file in the kernel stays the same. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'drivers/firmware/efi/Kconfig')
0 files changed, 0 insertions, 0 deletions