On Tue, Dec 11, 2018 at 12:03 PM Masahiro Yamada
> 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
> The majority of code already surround file paths with double quotes,
> and it makes sense since the included file paths are constant string
> Make it treewide consistent now.
> Signed-off-by: Masahiro Yamada <email@example.com>
> arch/m68k/Kconfig 6 +++---
Acked-by: Geert Uytterhoeven <firstname.lastname@example.org>