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
Date: Mon, 01 Mar 2021 15:05:54 -0700 [thread overview]
Message-ID: <878s7634xp.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210215172857.382285-1-linux@leemhuis.info>
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
next prev parent reply other threads:[~2021-03-02 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:28 [PATCH] docs: reporting-issues.rst: explain how to decode stack traces Thorsten Leemhuis
2021-02-23 11:57 ` Vlastimil Babka
2021-03-01 22:05 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-10 5:48 Thorsten Leemhuis
2021-02-11 17:07 ` Randy Dunlap
2021-02-15 5:25 ` Thorsten Leemhuis
2021-02-14 16:00 ` Qais Yousef
2021-02-15 5:55 ` Thorsten Leemhuis
2021-02-15 14:28 ` Qais Yousef
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=878s7634xp.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=linux@tometzki.de \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=vbabka@suse.cz \
/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