[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <878s7634xp.fsf@meer.lwn.net>
Date: Mon, 01 Mar 2021 15:05:54 -0700
From: Jonathan Corbet <corbet@....net>
To: Thorsten Leemhuis <linux@...mhuis.info>,
Randy Dunlap <rdunlap@...radead.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Sasha Levin <sashal@...nel.org>,
Vlastimil Babka <vbabka@...e.cz>,
Joerg Roedel <joro@...tes.org>,
Qais Yousef <qais.yousef@....com>,
Damian Tometzki <linux@...etzki.de>
Subject: Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack
traces
Thorsten Leemhuis <linux@...mhuis.info> writes:
> Replace placeholder text about decoding stack traces with a section that
> properly describes what a typical user should do these days. To make
> it works for them, add a paragraph in an earlier section to ensure
> people build their kernels with everything that's needed to decode stack
> traces later.
>
> Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
> Reviewed-by: Qais Yousef <qais.yousef@....com>
> ---
> v1->v2
> * Fix typo pointed out by Randy
> * include review feedback from Qais and bis Reviewed-by:
>
> v1:
> https://lore.kernel.org/lkml/20210210054823.242262-1-linux@leemhuis.info/
> ---
> .../admin-guide/reporting-issues.rst | 81 ++++++++++++++-----
> 1 file changed, 59 insertions(+), 22 deletions(-)
Applied, thanks.
jon
Powered by blists - more mailing lists