From: Jonathan Corbet <corbet@lwn.net>
To: hariconscious@gmail.com, shuah@kernel.org,
catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: HariKrishna <hariconscious@gmail.com>
Subject: Re: [PATCH] documentation/arm64 : kdump fixed typo errors
Date: Mon, 18 Aug 2025 10:08:21 -0600 [thread overview]
Message-ID: <871pp8a9ze.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250816120731.24508-1-hariconscious@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: hariconscious@gmail.com
To: corbet@lwn.net
Cc: catalin.marinas@arm.com, hariconscious@gmail.com,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, shuah@kernel.org, will@kernel.org
Subject: Re: [PATCH] documentation/arm64 : kdump fixed typo errors
Date: Mon, 8 Sep 2025 15:39:01 +0530 [thread overview]
Message-ID: <871pp8a9ze.fsf@trenco.lwn.net> (raw)
Message-ID: <20250908100901.S6OfbdZDM---Hza2K4csn9fb49aOm_4beg7we04gPF4@z> (raw)
In-Reply-To: <20250816120731.24508-1-hariconscious@gmail.com>
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
Hi Jon,
Good day.
Thanks for the suggestion, will correct and send the patch again.
And my real name is "HariKrishna" and see that it is mentioned in Signed-off-by tag.
Do I need to add surname as well ? Please let me know.
Thank you.
HariKrishna.
next prev parent reply other threads:[~2025-08-18 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 12:07 [PATCH] documentation/arm64 : kdump fixed typo errors hariconscious
2025-08-18 16:08 ` Jonathan Corbet [this message]
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=871pp8a9ze.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=catalin.marinas@arm.com \
--cc=hariconscious@gmail.com \
--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.