提交 e223a707 编写于 作者: T Thorsten Leemhuis 提交者: Jonathan Corbet

docs: reporting-issues: move 'outdated, need help' note to proper place

Move the 'this section is a placeholder for now and needs help by
someone with domain knowledge' note one section upwards to the place
where it belongs: the 'Decode failure messages' section.
Signed-off-by: NThorsten Leemhuis <linux@leemhuis.info>
Link: https://lore.kernel.org/r/d3894ba4a302beed661304cbcdc062c6dcfe3e58.1607489877.git.linux@leemhuis.infoSigned-off-by: NJonathan Corbet <corbet@lwn.net>
上级 547f574f
......@@ -923,18 +923,6 @@ instead you can join.
Decode failure messages
-----------------------
*If the failure includes a stack dump, like an Oops does, consider decoding
it to find the offending line of code.*
When the kernel detects an error, it will print a stack dump that allows to
identify the exact line of code where the issue happens. But that information
sometimes needs to get decoded to be readable, which is explained in
admin-guide/bug-hunting.rst.
Special care for regressions
----------------------------
.. note::
FIXME: The text in this section is a placeholder for now and quite similar to
......@@ -953,6 +941,18 @@ Special care for regressions
..
*If the failure includes a stack dump, like an Oops does, consider decoding
it to find the offending line of code.*
When the kernel detects an error, it will print a stack dump that allows to
identify the exact line of code where the issue happens. But that information
sometimes needs to get decoded to be readable, which is explained in
admin-guide/bug-hunting.rst.
Special care for regressions
----------------------------
*If your problem is a regression, try to narrow down when the issue was
introduced as much as possible.*
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册