[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210529110305.9446-4-thunder.leizhen@huawei.com>
Date: Sat, 29 May 2021 19:03:04 +0800
From: Zhen Lei <thunder.leizhen@...wei.com>
To: Jason Wessel <jason.wessel@...driver.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Douglas Anderson <dianders@...omium.org>,
Balbir Singh <bsingharora@...il.com>,
Barry Song <song.bao.hua@...ilicon.com>,
Christoph Hellwig <hch@....de>,
"Marek Szyprowski" <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Darren Hart <dvhart@...radead.org>,
Davidlohr Bueso <dave@...olabs.net>,
Eric Biederman <ebiederm@...ssion.com>,
"Naveen N . Rao" <naveen.n.rao@...ux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S . Miller" <davem@...emloft.net>,
Masami Hiramatsu <mhiramat@...nel.org>,
Jessica Yu <jeyu@...nel.org>,
"Steffen Klassert" <steffen.klassert@...unet.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Oleg Nesterov <oleg@...hat.com>,
John Stultz <john.stultz@...aro.org>,
Stephen Boyd <sboyd@...nel.org>,
Luis Chamberlain <mcgrof@...nel.org>,
Tejun Heo <tj@...nel.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
kgdb-bugreport <kgdb-bugreport@...ts.sourceforge.net>,
kexec <kexec@...ts.infradead.org>,
linux-crypto <linux-crypto@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
CC: Zhen Lei <thunder.leizhen@...wei.com>
Subject: [PATCH v2 3/4] kexec: fix a spelling mistake in comment
alloed ==> allowed
Signed-off-by: Zhen Lei <thunder.leizhen@...wei.com>
Acked-by: "Eric W. Biederman" <ebiederm@...ssion.com>
---
kernel/kexec_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index 4b34a9aa32bc..21d44f7ae8a8 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -180,7 +180,7 @@ int sanity_check_segment_list(struct kimage *image)
}
/* Verify our destination addresses do not overlap.
- * If we alloed overlapping destination addresses
+ * If we allowed overlapping destination addresses
* through very weird things can happen with no
* easy explanation as one segment stops on another.
*/
--
2.25.1
Powered by blists - more mailing lists