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;
Subject: Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack
 traces
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>
References: <20210210054823.242262-1-linux@leemhuis.info>
 <bd9a3e43-d52f-d947-04bc-28d4cc524cb4@infradead.org>
From:   Thorsten Leemhuis <linux@leemhuis.info>
Message-ID: <5092d5ef-e790-3833-87be-e067c3189d25@leemhuis.info>
Date:   Mon, 15 Feb 2021 06:25:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <bd9a3e43-d52f-d947-04bc-28d4cc524cb4@infradead.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

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