From: Geert Uytterhoeven Date: Tue, 8 Jun 2021 10:56:09 +0000 (+0200) Subject: nvme: NVME_TCP_OFFLOAD should not default to m X-Git-Tag: v5.14-rc1~119^2~287 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=762411542050dbe27c7c96f13c57f93da5d9b89a;p=thirdparty%2Fkernel%2Flinux.git nvme: NVME_TCP_OFFLOAD should not default to m The help text for the symbol controlling support for the NVM Express over Fabrics TCP offload common layer suggests to not enable this support when unsure. Hence drop the "default m", which actually means "default y" if CONFIG_MODULES is not enabled. Fixes: f0e8cb6106da2703 ("nvme-tcp-offload: Add nvme-tcp-offload - NVMeTCP HW offload ULP") Signed-off-by: Geert Uytterhoeven Signed-off-by: David S. Miller --- diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig index caedc35e1f0d0..a01e3f380e748 100644 --- a/drivers/nvme/host/Kconfig +++ b/drivers/nvme/host/Kconfig @@ -87,7 +87,6 @@ config NVME_TCP config NVME_TCP_OFFLOAD tristate "NVM Express over Fabrics TCP offload common layer" - default m depends on BLOCK depends on INET select NVME_CORE