From: Matthew Wilcox <willy@infradead.org>
To: Nir Lichtman <nir@lichtman.org>
Cc: jason.wessel@windriver.com, daniel.thompson@linaro.org,
dianders@chromium.org, corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: English fixes in kgdb/kdb article
Date: Fri, 18 Oct 2024 18:27:01 +0100 [thread overview]
Message-ID: <ZxKaZR_M-mOjSmBp@casper.infradead.org> (raw)
In-Reply-To: <20241018163136.GA795979@lichtman.org>
On Fri, Oct 18, 2024 at 04:31:36PM +0000, Nir Lichtman wrote:
> -Next you should choose one of more I/O drivers to interconnect debugging
> +Next you should choose one of the I/O drivers to interconnect the debugging
Wrong fix ;-) "one or more".
> @@ -201,7 +201,7 @@ Using loadable module or built-in
> Configure kgdboc at runtime with sysfs
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> -At run time you can enable or disable kgdboc by echoing a parameters
> +At run time you can enable or disable kgdboc by echoing the parameters
> into the sysfs. Here are two examples:
Maybe "by writing parameters into sysfs"?
> @@ -631,8 +631,6 @@ automatically changes into kgdb mode.
>
> kgdb
>
> - Now disconnect your terminal program and connect gdb in its place
> -
Is there a reason you deleted this? It seems important.
next prev parent reply other threads:[~2024-10-18 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:31 [PATCH] Documentation: English fixes in kgdb/kdb article Nir Lichtman
2024-10-18 17:27 ` Matthew Wilcox [this message]
2024-10-18 17:49 ` Nir Lichtman
2024-10-18 17:56 ` Matthew Wilcox
2024-10-18 17:55 ` [PATCH v2] " Nir Lichtman
2024-10-18 19:46 ` Doug Anderson
2024-10-18 22:21 ` Nir Lichtman
2024-10-18 22:35 ` [PATCH v3] " Nir Lichtman
2024-10-18 22:49 ` Doug Anderson
2024-10-18 23:10 ` Jonathan Corbet
2024-10-19 5:50 ` Nir Lichtman
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=ZxKaZR_M-mOjSmBp@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@lichtman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox