[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1605519767-25502-1-git-send-email-yangtiezhu@loongson.cn>
Date: Mon, 16 Nov 2020 17:42:47 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Jason Wessel <jason.wessel@...driver.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Douglas Anderson <dianders@...omium.org>,
Jonathan Corbet <corbet@....net>
Cc: kgdb-bugreport@...ts.sourceforge.net, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Xuefeng Li <lixuefeng@...ngson.cn>,
Sergei Shtylyov <sergei.shtylyov@...il.com>
Subject: [PATCH] Documentation: kgdb: Fix a typo
"to into" -> "into"
Reported-by: Sergei Shtylyov <sergei.shtylyov@...il.com>
Signed-off-by: Tiezhu Yang <yangtiezhu@...ngson.cn>
---
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
Powered by blists - more mailing lists