Commit e223a707 authored by Thorsten Leemhuis's avatar Thorsten Leemhuis Committed by Jonathan Corbet
Browse files

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: default avatarThorsten Leemhuis <linux@leemhuis.info>
Link: https://lore.kernel.org/r/d3894ba4a302beed661304cbcdc062c6dcfe3e58.1607489877.git.linux@leemhuis.info


Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 547f574f
Loading
Loading
Loading
Loading
+12 −12
Original line number Diff line number Diff line
@@ -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.*