[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250727023019.82233-1-ignacio.pena87@gmail.com>
Date: Sat, 26 Jul 2025 22:30:19 -0400
From: Ignacio Peña <ignacio.pena87@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Ignacio Pena <ignacio.pena87@...il.com>
Subject: [PATCH] drivers/cpufreq/qcom-cpufreq-nvmem.c: Fix typo 'defered' -> 'deferred'
Fix spelling mistake.
No functional change.
Signed-off-by: Ignacio Pena <ignacio.pena87@...il.com>
---
drivers/cpufreq/qcom-cpufreq-nvmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
index 54f811710..5a711de3e 100644
--- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
+++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
@@ -605,7 +605,7 @@ MODULE_DEVICE_TABLE(of, qcom_cpufreq_match_list);
/*
* Since the driver depends on smem and nvmem drivers, which may
* return EPROBE_DEFER, all the real activity is done in the probe,
- * which may be defered as well. The init here is only registering
+ * which may be deferred as well. The init here is only registering
* the driver and the platform device.
*/
static int __init qcom_cpufreq_init(void)
--
2.50.1
Powered by blists - more mailing lists