From: Thorsten Leemhuis <linux@leemhuis.info>
To: Randy Dunlap <rdunlap@infradead.org>, Jonathan Corbet <corbet@lwn.net>
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, 15 Feb 2021 06:25:46 +0100 [thread overview]
Message-ID: <5092d5ef-e790-3833-87be-e067c3189d25@leemhuis.info> (raw)
In-Reply-To: <bd9a3e43-d52f-d947-04bc-28d4cc524cb4@infradead.org>
Am 11.02.21 um 18:07 schrieb Randy Dunlap:
> Just a couple of small nits (or one that is repeated):
:-D
> On 2/9/21 9:48 PM, Thorsten Leemhuis wrote:
>>
>> - * If the failure includes a stack dump, like an Oops does, consider decoding
>> - it to find the offending line of code.
>> + * If your failure involves a 'panic', 'oops', or 'warning', consider decoding
>> + the kernel log to find the line of code that trigger the error.
> triggered
> […]
> or it could be "code that triggers"... (just not "trigger").
Ahh, yes, you're right of course. Went with the former, many thx for
taking a look and pointing it out!
Ciao, Thorsten
next prev parent reply other threads:[~2021-02-15 5:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 5:48 Thorsten Leemhuis
2021-02-11 17:07 ` Randy Dunlap
2021-02-15 5:25 ` Thorsten Leemhuis [this message]
2021-02-14 16:00 ` Qais Yousef
2021-02-15 5:55 ` Thorsten Leemhuis
2021-02-15 14:28 ` Qais Yousef
2021-02-15 17:28 Thorsten Leemhuis
2021-02-23 11:57 ` Vlastimil Babka
2021-03-01 22:05 ` Jonathan Corbet
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=5092d5ef-e790-3833-87be-e067c3189d25@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®