[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bhmgv3myrraschcaenvaq2sfpslcbedcsca2hirxau6gu56xbu@a54h2sj2xoz3>
Date: Thu, 16 Jan 2025 17:41:28 +0800
From: Jiayuan Chen <mrpre@....com>
To: Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] docs/arch: remove deprecated function name
On Tue, Jan 14, 2025 at 10:11:01AM +0800, Jonathan Corbet wrote:
> Jiayuan Chen <mrpre@....com> writes:
>
> >
> > 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
You're right.
As Randy mentioned, printk_stack_address() can probably be used as a
drop-in replacement for the original function, and I found that it hasn't
been touched since 3.12 anyway.
Powered by blists - more mailing lists