From: Daniel Thompson <daniel.thompson@linaro.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Douglas Anderson <dianders@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
kgdb-bugreport@lists.sourceforge.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>
Subject: Re: [PATCH] Documentation: kgdb: Fix a typo
Date: Mon, 16 Nov 2020 09:47:36 +0000 [thread overview]
Message-ID: <20201116094736.hmqnyl3xezeupzyb@holly.lan> (raw)
In-Reply-To: <1605519767-25502-1-git-send-email-yangtiezhu@loongson.cn>
On Mon, Nov 16, 2020 at 05:42:47PM +0800, Tiezhu Yang wrote:
> "to into" -> "into"
>
> Reported-by: Sergei Shtylyov <sergei.shtylyov@gmail.com>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> Documentation/dev-tools/kgdb.rst | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/dev-tools/kgdb.rst b/Documentation/dev-tools/kgdb.rst
> index 77b688e..4345624 100644
> --- a/Documentation/dev-tools/kgdb.rst
> +++ b/Documentation/dev-tools/kgdb.rst
> @@ -63,10 +63,9 @@ will want to turn on ``CONFIG_DEBUG_INFO`` which is called
> It is advised, but not required, that you turn on the
> ``CONFIG_FRAME_POINTER`` kernel option which is called :menuselection:`Compile
> the kernel with frame pointers` in the config menu. This option inserts code
> -to into the compiled executable which saves the frame information in
> -registers or on the stack at different points which allows a debugger
> -such as gdb to more accurately construct stack back traces while
> -debugging the kernel.
> +into the compiled executable which saves the frame information in registers
> +or on the stack at different points which allows a debugger such as gdb to
> +more accurately construct stack back traces while debugging the kernel.
>
> If the architecture that you are using supports the kernel option
> ``CONFIG_STRICT_KERNEL_RWX``, you should consider turning it off. This
> --
> 2.1.0
>
next prev parent reply other threads:[~2020-11-16 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 9:42 [PATCH] Documentation: kgdb: Fix a typo Tiezhu Yang
2020-11-16 9:47 ` Daniel Thompson [this message]
2020-11-18 20:48 ` 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=20201116094736.hmqnyl3xezeupzyb@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=sergei.shtylyov@gmail.com \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).