* [PATCH] docs: reporting-issues: move 'outdated, need help' note to proper place
@ 2020-12-09 5:19 Thorsten Leemhuis
2020-12-10 0:25 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Leemhuis @ 2020-12-09 5:19 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-doc, linux-kernel
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>
---
Brown paper bag fixup :-/
---
.../admin-guide/reporting-issues.rst | 24 +++++++++----------
1 file 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.*
base-commit: 547f574fd9d5e3925d47fd44decbf6ab6df94b0e
--
2.29.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] docs: reporting-issues: move 'outdated, need help' note to proper place
2020-12-09 5:19 [PATCH] docs: reporting-issues: move 'outdated, need help' note to proper place Thorsten Leemhuis
@ 2020-12-10 0:25 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2020-12-10 0:25 UTC (permalink / raw)
To: Thorsten Leemhuis; +Cc: linux-doc, linux-kernel
On Wed, 9 Dec 2020 06:19:14 +0100
Thorsten Leemhuis <linux@leemhuis.info> wrote:
> 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>
> ---
> Brown paper bag fixup :-/
Hey, if it's the only one we're in fine shape :)
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-10 0:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-09 5:19 [PATCH] docs: reporting-issues: move 'outdated, need help' note to proper place Thorsten Leemhuis
2020-12-10 0:25 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).