Idea and text comes from
Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst

Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
 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 <linux@leemhuis.info>, know by email while ideally CCing
+the public Linux docs mailing list <linux-doc@vger.kernel.org>. 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

Thorsten Leemhuis <linux@leemhuis.info> writes:

> Idea and text comes from
> Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
>  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 <linux@leemhuis.info>, know by email while ideally CCing
> +the public Linux docs mailing list <linux-doc@vger.kernel.org>. 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.
> +

Consider also soliciting patches to improve it - one can always hope we
can bring in some help...

Thanks,

jon

On 10/27/25 18:29, Jonathan Corbet wrote:
> Thorsten Leemhuis <linux@leemhuis.info> writes:
[...]
>> +If any of that applies, please take a moment and let the primary author of this
>> +text, Thorsten Leemhuis <linux@leemhuis.info>, know by email while ideally CCing
>> +the public Linux docs mailing list <linux-doc@vger.kernel.org>. 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.
>> +
> 
> Consider also soliciting patches to improve it - one can always hope we
> can bring in some help...

Yeah, valid point, will use this:

If any of that applies, please let the developers know by
sending a short note or a patch to Thorsten Leemhuis
<linux@leemhuis.info> while ideally CCing the public Linux docs mailing
list <linux-doc@vger.kernel.org>.

And include a patch in the next submission that updates two other places
in the docs that use nearly the identical text.

Ciao, Thorsten