Documentation/arch/arm64/kdump.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
From: HariKrishna <hariconscious@gmail.com>
kdump.rst documentation typos corrected
Signed-off-by: HariKrishna <hariconscious@gmail.com>
---
Documentation/arch/arm64/kdump.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arch/arm64/kdump.rst b/Documentation/arch/arm64/kdump.rst
index 56a89f45df28..d3195a93a066 100644
--- a/Documentation/arch/arm64/kdump.rst
+++ b/Documentation/arch/arm64/kdump.rst
@@ -5,7 +5,7 @@ crashkernel memory reservation on arm64
Author: Baoquan He <bhe@redhat.com>
Kdump mechanism is used to capture a corrupted kernel vmcore so that
-it can be subsequently analyzed. In order to do this, a preliminarily
+it can be subsequently analyzed. In order to do this, a preliminary
reserved memory is needed to pre-load the kdump kernel and boot such
kernel if corruption happens.
@@ -18,7 +18,7 @@ Kernel parameter
Through the kernel parameters below, memory can be reserved accordingly
during the early stage of the first kernel booting so that a continuous
-large chunk of memomy can be found. The low memory reservation needs to
+large chunk of memory can be found. The low memory reservation needs to
be considered if the crashkernel is reserved from the high memory area.
- crashkernel=size@offset
--
2.43.0
hariconscious@gmail.com writes: > From: HariKrishna <hariconscious@gmail.com> > > kdump.rst documentation typos corrected > > Signed-off-by: HariKrishna <hariconscious@gmail.com> > --- > Documentation/arch/arm64/kdump.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/arch/arm64/kdump.rst b/Documentation/arch/arm64/kdump.rst > index 56a89f45df28..d3195a93a066 100644 > --- a/Documentation/arch/arm64/kdump.rst > +++ b/Documentation/arch/arm64/kdump.rst > @@ -5,7 +5,7 @@ crashkernel memory reservation on arm64 > Author: Baoquan He <bhe@redhat.com> > > Kdump mechanism is used to capture a corrupted kernel vmcore so that > -it can be subsequently analyzed. In order to do this, a preliminarily > +it can be subsequently analyzed. In order to do this, a preliminary > reserved memory is needed to pre-load the kdump kernel and boot such > kernel if corruption happens. I don't think this is right. While reserving judgment on "preliminarily" as a word, the intended use is adverbial, so this change does not make things better. The better fix, perhaps, is to say "previously" instead. Should you choose to resubmit this, we'll need your real name in the Signed-off-by tag, please. Thanks, jon
© 2016 - 2025 Red Hat, Inc.