aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/interrupts.py
diff options
context:
space:
mode:
authorArnd Bergmann <[email protected]>2023-11-22 23:47:18 +0100
committerJens Axboe <[email protected]>2023-11-22 18:40:14 -0700
commit65e2a74c44ddfa174b700f5da2d1d29b4ba6639b (patch)
tree7ed75a0f52739d0f68dd04d331b9eea826a86dc0 /scripts/gdb/linux/interrupts.py
parentd78abcbabe7e98bb4baa4dea87550806944790ed (diff)
nvme: target: fix Kconfig select statements
When the NVME target code is built-in but its TCP frontend is a loadable module, enabling keyring support causes a link failure: x86_64-linux-ld: vmlinux.o: in function `nvmet_ports_make': configfs.c:(.text+0x100a211): undefined reference to `nvme_keyring_id' The problem is that CONFIG_NVME_TARGET_TCP_TLS is a 'bool' symbol that depends on the tristate CONFIG_NVME_TARGET_TCP, so any 'select' from it inherits the state of the tristate symbol rather than the intended CONFIG_NVME_TARGET one that contains the actual call. The same thing is true for CONFIG_KEYS, which itself is required for NVME_KEYRING. Signed-off-by: Arnd Bergmann <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/interrupts.py')
0 files changed, 0 insertions, 0 deletions