All of lore.kernel.org
 help / color / mirror / Atom feed
From: hariconscious@gmail.com
To: shuah@kernel.org, catalin.marinas@arm.com, will@kernel.org,
	corbet@lwn.net, linux-arm-kernel@lists.infradead.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: HariKrishna <hariconscious@gmail.com>
Subject: [PATCH] documentation/arm64 : kdump fixed typo errors
Date: Sat, 16 Aug 2025 17:37:31 +0530	[thread overview]
Message-ID: <20250816120731.24508-1-hariconscious@gmail.com> (raw)

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



             reply	other threads:[~2025-08-16 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 12:07 hariconscious [this message]
2025-08-18 16:08 ` [PATCH] documentation/arm64 : kdump fixed typo errors Jonathan Corbet
2025-09-08 10:09   ` hariconscious
2025-09-08  9:54   ` hariconscious
2025-09-08 13:23     ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250816120731.24508-1-hariconscious@gmail.com \
    --to=hariconscious@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.