summaryrefslogtreecommitdiff
path: root/crypto/Kconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2018-12-11 20:01:04 +0900
committerMasahiro Yamada <yamada.masahiro@socionext.com>2018-12-22 00:25:54 +0900
commit5bee4f1ec51218e7de50cab5fc9f770ebb44c0f3 (patch)
treedec377ae83ce7283d818208ed27a0b11f4a4c868 /crypto/Kconfig
parentc7ef39a437ecd8db2f7f3c7b36cbcc1eeb525636 (diff)
downloadlinux-crypto-5bee4f1ec51218e7de50cab5fc9f770ebb44c0f3.tar.gz
linux-crypto-5bee4f1ec51218e7de50cab5fc9f770ebb44c0f3.zip
treewide: surround Kconfig file paths with double quotes
The Kconfig lexer supports special characters such as '.' and '/' in the parameter context. In my understanding, the reason is just to support bare file paths in the source statement. I do not see a good reason to complicate Kconfig for the room of ambiguity. The majority of code already surrounds file paths with double quotes, and it makes sense since file paths are constant string literals. Make it treewide consistent now. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Wolfram Sang <wsa@the-dreams.de> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> Acked-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'crypto/Kconfig')
-rw-r--r--crypto/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/crypto/Kconfig b/crypto/Kconfig
index f7a235db..2c63b52a 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -1826,7 +1826,7 @@ config CRYPTO_HASH_INFO
bool
source "drivers/crypto/Kconfig"
-source crypto/asymmetric_keys/Kconfig
-source certs/Kconfig
+source "crypto/asymmetric_keys/Kconfig"
+source "certs/Kconfig"
endif # if CRYPTO