[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210317084016.3787380-1-unixbhaskar@gmail.com>
Date: Wed, 17 Mar 2021 14:10:16 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: fenghua.yu@...el.com, reinette.chatre@...el.com,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org,
hpa@...or.com, linux-kernel@...r.kernel.org
Cc: rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH] kernel: cpu: resctrl: Minor typo fix in the file pseudo_lock.c
s/derefence/dereference/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
arch/x86/kernel/cpu/resctrl/pseudo_lock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
index e916646adc69..43990a882b36 100644
--- a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
+++ b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
@@ -1307,7 +1307,7 @@ int rdtgroup_pseudo_lock_create(struct rdtgroup *rdtgrp)
* If the thread does not get on the CPU for whatever
* reason and the process which sets up the region is
* interrupted then this will leave the thread in runnable
- * state and once it gets on the CPU it will derefence
+ * state and once it gets on the CPU it will dereference
* the cleared, but not freed, plr struct resulting in an
* empty pseudo-locking loop.
*/
--
2.30.2
Powered by blists - more mailing lists