[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250114094832.350073-1-mrpre@163.com>
Date: Tue, 14 Jan 2025 17:48:32 +0800
From: Jiayuan Chen <mrpre@....com>
To: linux-doc@...r.kernel.org
Cc: tglx@...utronix.de,
mingo@...hat.com,
bp@...en8.de,
dave.hansen@...ux.intel.com,
x86@...nel.org,
hpa@...or.com,
corbet@....net,
linux-kernel@...r.kernel.org,
Jiayuan Chen <mrpre@....com>
Subject: [PATCH v1] docs/arch: remove deprecated function name
The dumpstack.c file has undergone many modifications, and the
print_context_stack() function was removed or rewritten a long time ago,
so it's better to remove the incorrect guidance. Additionally, no new
functions will be added to the documentation, as it may be modified again
in the future. Using 'question mark' and 'dumpstack' is sufficient to
index this document.
Signed-off-by: Jiayuan Chen <mrpre@....com>
---
Documentation/arch/x86/kernel-stacks.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/arch/x86/kernel-stacks.rst b/Documentation/arch/x86/kernel-stacks.rst
index 738671a4070b..2d355e78008e 100644
--- a/Documentation/arch/x86/kernel-stacks.rst
+++ b/Documentation/arch/x86/kernel-stacks.rst
@@ -113,7 +113,7 @@ Printing backtraces on x86
The question about the '?' preceding function names in an x86 stacktrace
keeps popping up, here's an indepth explanation. It helps if the reader
-stares at print_context_stack() and the whole machinery in and around
+stares at 'question mark' and the whole machinery in and around
arch/x86/kernel/dumpstack.c.
Adapted from Ingo's mail, Message-ID: <20150521101614.GA10889@...il.com>:
--
2.43.5
Powered by blists - more mailing lists