linux-kernel - Re: [PATCH v1 03/30] docs: reporting-issues: add conclusion to the step-by-step guide

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ms5cntho.fsf@trenco.lwn.net>
Date: Mon, 27 Oct 2025 11:29:23 -0600
From: Jonathan Corbet <corbet@....net>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: workflows@...r.kernel.org, linux-doc@...r.kernel.org,
 regressions@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 03/30] docs: reporting-issues: add conclusion to the
 step-by-step guide

Thorsten Leemhuis <linux@...mhuis.info> writes:

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