summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide/reporting-issues.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/admin-guide/reporting-issues.rst')
-rw-r--r--Documentation/admin-guide/reporting-issues.rst24
1 files changed, 12 insertions, 12 deletions
diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index 5cbb1b5f4a52..07879d01fe68 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -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.*