linux-kernel - [PATCH v1 0/3] docs: verify/bisect: fine tuning, testing fixes, and using a build host

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-next>] [day] [month] [year] [list]

Date: Mon,  1 Apr 2024 11:29:40 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Jonathan Corbet <corbet@....net>
Cc: regressions@...ts.linux.dev,
	linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Bagas Sanjaya <bagasdotme@...il.com>,
	Petr Tesařík <petr@...arici.cz>
Subject: [PATCH v1 0/3] docs: verify/bisect: fine tuning, testing fixes, and using a build host

A quick series with various improvements for
Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst.

* The first patch contains various fixes and some fine tuning.

* The second adds a few instructions for later testing of reverts,
  fixes, or newer versions. This was already hinted at; but during some
  early work on Documentation/admin-guide/reporting-issues.rst to better
  reconcile the two it seemed wise to cover this properly here.

* The third patch briefly outlines how to build kernels on a different
  host; it came into being after a second user within one week asked for
  this. That also allowed the text to briefly cover cross-compilation.
---

Hi! While at it let me mention one more thing unrelated to the changes
where I'm unsure if the current approach by the text was a wise choice:

* Should the document tell users to avoid mainline during merge windows?

Some input from the community on this would be splendid.

Ciao, Thorsten

P.S.: Not totally sure, but I think this should go into 6.9 as this is
a new document; but I can split this up if the two latter patches better
should go into -next.

Thorsten Leemhuis (3):
  docs: verify/bisect: git switch; proper headlines; various fixes;
  docs: verify/bisect: explain testing reverts, patches and newer code
  docs: verify/bisect: describe how to use a build host

 .../verify-bugs-and-bisect-regressions.rst    | 469 +++++++++++++-----
 1 file changed, 344 insertions(+), 125 deletions(-)

base-commit: b8cfda5c9065cd619a97c17da081cbfab3b1e756
-- 
2.44.0