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
