Idea and text comes from Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
Signed-off-by: Thorsten Leemhuis <[email protected]> --- Documentation/admin-guide/reporting-issues.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst index 90b50c27c0d2b6..9676ba85e1b73c 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 take a moment and let the primary author of this +text, Thorsten Leemhuis <[email protected]>, know by email while ideally CCing +the public Linux docs mailing list <[email protected]>. 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 ============================================================= -- 2.51.0
