summaryrefslogtreecommitdiffstats
path: root/drivers/nvme/host
diff options
context:
space:
mode:
authorJean Delvare <jdelvare@suse.de>2020-02-11 13:41:36 +0100
committerKeith Busch <kbusch@kernel.org>2020-03-25 20:45:25 +0100
commit228914504cecd1c7d1279b5b884ab55d474cc87e (patch)
tree8f9058ee7af08fd0e3d0f2d56dc639d04124c636 /drivers/nvme/host
parentnvme: expose hostid via sysfs for fabrics controllers (diff)
downloadlinux-228914504cecd1c7d1279b5b884ab55d474cc87e.tar.xz
linux-228914504cecd1c7d1279b5b884ab55d474cc87e.zip
nvme: Don't deter users from enabling hwmon support
I see no good reason for the "If unsure, say N" advice in the description of the NVME_HWMON configuration option. It is not dangerous, it does not select any other option, and has a fairly low overhead. As the option is already not enabled by default, further suggesting hesitant users to not enable it is not useful anyway. Unlike some other options where the description alone may not be sufficient for users to make a decision, NVME_HWMON is pretty simple to grasp in my opinion, so just let the user do what they want. Signed-off-by: Jean Delvare <jdelvare@suse.de> Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Cc: Christoph Hellwig <hch@lst.de> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'drivers/nvme/host')
-rw-r--r--drivers/nvme/host/Kconfig2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
index b9358db83e96..9c17ed32be64 100644
--- a/drivers/nvme/host/Kconfig
+++ b/drivers/nvme/host/Kconfig
@@ -32,8 +32,6 @@ config NVME_HWMON
a hardware monitoring device will be created for each NVMe drive
in the system.
- If unsure, say N.
-
config NVME_FABRICS
tristate