Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Jonathan Corbet <corbet@lwn.net>
To:     Thorsten Leemhuis <linux@leemhuis.info>,
        Randy Dunlap <rdunlap@infradead.org>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        Sasha Levin <sashal@kernel.org>,
        Vlastimil Babka <vbabka@suse.cz>,
        Joerg Roedel <joro@8bytes.org>,
        Qais Yousef <qais.yousef@arm.com>,
        Damian Tometzki <linux@tometzki.de>
Subject: Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack
 traces
In-Reply-To: <20210215172857.382285-1-linux@leemhuis.info>
References: <20210215172857.382285-1-linux@leemhuis.info>
Date:   Mon, 01 Mar 2021 15:05:54 -0700
Message-ID: <878s7634xp.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Thorsten Leemhuis <linux@leemhuis.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@leemhuis.info>
> Reviewed-by: Qais Yousef <qais.yousef@arm.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