diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-11 12:01:05 +0100 |
|---|---|---|
| committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-21 16:25:54 +0100 |
| commit | f5451582c4e22ce8912aae4950810f3598c9b516 (patch) | |
| tree | fce36383fca69f12a703ec061fdadc6cb691e78f /scripts/kconfig/preprocess.c | |
| parent | treewide: surround Kconfig file paths with double quotes (diff) | |
| download | linux-f5451582c4e22ce8912aae4950810f3598c9b516.tar.xz linux-f5451582c4e22ce8912aae4950810f3598c9b516.zip | |
kconfig: stop supporting '.' and '/' in unquoted words
In my understanding, special characters such as '.' and '/' are
supported in unquoted words to use bare file paths in the "source"
statement.
With the previous commit surrounding all file paths with double
quotes, we can drop this.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'scripts/kconfig/preprocess.c')
| -rw-r--r-- | scripts/kconfig/preprocess.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/scripts/kconfig/preprocess.c b/scripts/kconfig/preprocess.c index 5ca2df790d3c..b028a48b0e76 100644 --- a/scripts/kconfig/preprocess.c +++ b/scripts/kconfig/preprocess.c @@ -555,8 +555,7 @@ char *expand_string(const char *in) static bool is_end_of_token(char c) { - /* Why are '.' and '/' valid characters for symbols? */ - return !(isalnum(c) || c == '_' || c == '-' || c == '.' || c == '/'); + return !(isalnum(c) || c == '_' || c == '-'); } /* |