diff options
| author | Arnd Bergmann <[email protected]> | 2025-07-26 21:10:43 +0000 |
|---|---|---|
| committer | Bartosz Golaszewski <[email protected]> | 2025-07-27 08:27:04 +0000 |
| commit | a86240a37d43fc22b4e4953242fca8d90df2c555 (patch) | |
| tree | f0feaedde8ee45c95e817acb3a8510de4ddc901d /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | gpio: virtio: Fix config space reading. (diff) | |
| download | kernel-a86240a37d43fc22b4e4953242fca8d90df2c555.tar.gz kernel-a86240a37d43fc22b4e4953242fca8d90df2c555.zip | |
gpiolib: enable CONFIG_GPIOLIB_LEGACY even for !GPIOLIB
A few drivers that use the legacy GPIOLIB interfaces can be enabled
even when GPIOLIB is disabled entirely. With my previous patch this
now causes build failures like:
drivers/nfc/s3fwrn5/uart.c: In function 's3fwrn82_uart_parse_dt':
drivers/nfc/s3fwrn5/uart.c:100:14: error: implicit declaration of function 'gpio_is_valid'; did you mean 'uuid_is_valid'? [-Werror=implicit-function-declaration]
These did not show up in my randconfig tests because randconfig almost
always has GPIOLIB selected by some other driver, and I did most
of the testing with follow-up patches that address the failures
properly.
Move the symbol outside of the 'if CONFIG_GPIOLIB' block for the moment
to avoid the build failures. It can be moved back and turned off by
default once all the driver specific changes are merged.
Reported-by: kernel test robot <[email protected]>
Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
Fixes: 678bae2eaa81 ("gpiolib: make legacy interfaces optional")
Signed-off-by: Arnd Bergmann <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Bartosz Golaszewski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions