The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jiayuan Chen <mrpre@163.com>, linux-doc@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	linux-kernel@vger.kernel.org, Jiayuan Chen <mrpre@163.com>
Subject: Re: [PATCH v1] docs/arch: remove deprecated function name
Date: Tue, 14 Jan 2025 10:11:01 -0700	[thread overview]
Message-ID: <8734hl9v8a.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250114094832.350073-1-mrpre@163.com>

Jiayuan Chen <mrpre@163.com> writes:

> 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@163.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.

Maybe - probably - I'm missing something, but I don't see how this is
going to help our readers?  If there *is* a function that will, by
virtue of being stared at, help bring enlightenment, why wouldn't we
name it?

Thanks,

jon

  reply	other threads:[~2025-01-14 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  9:48 [PATCH v1] docs/arch: remove deprecated function name Jiayuan Chen
2025-01-14 17:11 ` Jonathan Corbet [this message]
2025-01-16  9:41   ` Jiayuan Chen
2025-01-14 19:13 ` Randy Dunlap
2025-01-16 16:20 ` [PATCH v2] " Jiayuan Chen
2025-02-06  0:33   ` Randy Dunlap

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=8734hl9v8a.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mrpre@163.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox