From: Thorsten Leemhuis Date: Tue, 17 Mar 2026 12:33:06 +0000 (+0100) Subject: docs: reporting-issues: add conclusion to the step-by-step guide X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ceee0f73c3c6c45d4ffa4ebaf28a9094e0934779;p=thirdparty%2Fkernel%2Flinux.git docs: reporting-issues: add conclusion to the step-by-step guide Text based on a section Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst and slightly improved after review feedback. Signed-off-by: Thorsten Leemhuis Signed-off-by: Jonathan Corbet Message-ID: --- diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst index 9f9c5db25a6c1..aa058b295c5f3 100644 --- a/Documentation/admin-guide/reporting-issues.rst +++ b/Documentation/admin-guide/reporting-issues.rst @@ -241,6 +241,20 @@ kernels regularly rebased on those. If that is the case, follow these steps: The reference section below explains each of these steps in more detail. +Conclusion of the step-by-step guide +------------------------------------ + +Did you run into trouble following the step-by-step guide not cleared up by the +reference section below? Did you spot errors? Or do you have ideas on how to +improve the guide? + +If any of that applies, please let the developers know by sending a short note +or a patch to Thorsten Leemhuis while ideally CCing the +public Linux docs mailing list . Such feedback is +vital to improve this text further, which is in everybody's interest, as it will +enable more people to master the task described here. + + Reference section: Reporting issues to the kernel maintainers =============================================================