Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-03-01 Thread Jonathan Corbet
Thorsten Leemhuis 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 need

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-23 Thread Vlastimil Babka
On 2/15/21 6:28 PM, Thorsten Leemhuis wrote: > 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 every

[PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-15 Thread Thorsten Leemhuis
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. Si

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-15 Thread Qais Yousef
Hi Thorsten On 02/15/21 06:55, Thorsten Leemhuis wrote: > Hi! Many thx for looking into this, much appreciated! > > Am 14.02.21 um 17:00 schrieb Qais Yousef: > > On 02/10/21 06:48, Thorsten Leemhuis wrote: > > > >> - * If the failure includes a stack dump, like an Oops does, consider > >> decodi

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-14 Thread Thorsten Leemhuis
Hi! Many thx for looking into this, much appreciated! Am 14.02.21 um 17:00 schrieb Qais Yousef: > On 02/10/21 06:48, 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

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-14 Thread Thorsten Leemhuis
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

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-14 Thread Qais Yousef
On 02/10/21 06:48, Thorsten Leemhuis wrote: > 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 everyt

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-11 Thread Randy Dunlap
Hi Thorsten, Just a couple of small nits (or one that is repeated): On 2/9/21 9:48 PM, Thorsten Leemhuis wrote: > 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

[PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-09 Thread Thorsten Leemhuis
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. Si