[PATCH v2 3/3] nvmem: Replace eight spaces with a tab in Kconfig

From: Link Mauve

Date: Mon Oct 12 2026 - 17:13:03 EST


The NVMEM_QCOM_SEC_QFPROM driver was indented with eight spaces instead
of one tabulation character, and had been that way ever since its
inception in c471245bd9f25152e398fb49f65cf6e1ed7febbd.

Signed-off-by: Link Mauve <linkmauve@xxxxxxxxxxxx>
---
drivers/nvmem/Kconfig | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index ed5b8e21ded0..ff6c4c04cea9 100644
--- a/drivers/nvmem/Kconfig
+++ b/drivers/nvmem/Kconfig
@@ -389,17 +389,17 @@ config NVMEM_QCOM_QFPROM
will be called nvmem_qfprom.

config NVMEM_QCOM_SEC_QFPROM
- tristate "Qualcomm SECURE QFPROM Support"
- depends on ARCH_QCOM || COMPILE_TEST
- depends on HAS_IOMEM
- depends on OF
- select QCOM_SCM
- help
- Say y here to enable secure QFPROM support. The secure QFPROM provides access
- functions for QFPROM data to rest of the drivers via nvmem interface.
-
- This driver can also be built as a module. If so, the module will be called
- nvmem_sec_qfprom.
+ tristate "Qualcomm SECURE QFPROM Support"
+ depends on ARCH_QCOM || COMPILE_TEST
+ depends on HAS_IOMEM
+ depends on OF
+ select QCOM_SCM
+ help
+ Say y here to enable secure QFPROM support. The secure QFPROM provides access
+ functions for QFPROM data to rest of the drivers via nvmem interface.
+
+ This driver can also be built as a module. If so, the module will be called
+ nvmem_sec_qfprom.

config NVMEM_QNAP_MCU_EEPROM
tristate "QNAP MCU EEPROM Support"
--
2.56.0