diff options
| author | Stephen Warren | 2020-07-08 15:45:56 -0600 |
|---|---|---|
| committer | Tom Rini | 2020-07-17 10:47:19 -0400 |
| commit | 76ae74d348a05c8c9deb718368a69ba05afd9784 (patch) | |
| tree | 47464506cc5164993d550804deb2b850246a7db1 /configs/tuxx1_defconfig | |
| parent | dd85dc55eb147cdcced1a4ee143b487d4aa6afa6 (diff) | |
fixdep: fix CONFIG_IS_ENABLED etc. handling
When fixdep detects CONFIG_IS_ENABLED and other similar macros, it must
parse the macro parameter to determine which actual CONFIG_ option is
being referenced. This involves moving a pointer forward through the
entire CONFIG_ option "word". Currently, the code uses variable q to walk
through the word, but doesn't actually initialize it to point at the
parameter before doing so. Consequently, the walking process immediately
fails since it sees the macro invocatoins's ( rather than the expected
alpha-numeric characters in the macro parameter. Fix this by adding the
missing initialization.
Fixes: 67f2ee86ccbe ("kbuild: fixdep: Resync this with v4.17")
Fixes: 7012865e961c ("gpio: fix test.py for gpio label lookup")
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'configs/tuxx1_defconfig')
0 files changed, 0 insertions, 0 deletions