summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorThorsten Leemhuis <linux@leemhuis.info>2020-12-09 08:19:14 +0300
committerJonathan Corbet <corbet@lwn.net>2020-12-10 03:25:05 +0300
commite223a707ad84a1b45704e02220ea0cfe1b9cfbdd (patch)
tree2af7f7c87d96ef53a8c23b2d4f8ef84ccf259462 /Documentation/admin-guide
parent547f574fd9d5e3925d47fd44decbf6ab6df94b0e (diff)
downloadlinux-e223a707ad84a1b45704e02220ea0cfe1b9cfbdd.tar.xz
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: Thorsten Leemhuis <linux@leemhuis.info> Link: https://lore.kernel.org/r/d3894ba4a302beed661304cbcdc062c6dcfe3e58.1607489877.git.linux@leemhuis.info Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/admin-guide')
-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.*