linux-kernel - Re: linus-next: improving functional testing for to-be-merged pull requests

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: <ca2ca07c-33c9-4d67-80b3-f8c506938ba5@sirena.org.uk>
Date: Tue, 22 Oct 2024 14:19:08 +0100
From: Mark Brown <broonie@...nel.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: torvalds@...ux-foundation.org, ksummit@...ts.linux.dev,
	linux-kernel@...r.kernel.org, Sasha Levin <sashal@...nel.org>
Subject: Re: linus-next: improving functional testing for to-be-merged pull
 requests

On Tue, Oct 22, 2024 at 11:10:36AM +0200, Thorsten Leemhuis wrote:

> I wonder if part of this is a "don't know how to do that" aka "lack of
> documentation" problem. I've recently seen some good guide or mailing
> list post how to bisect -next somewhere, but I think it wasn't in our
> Documentation/ directory. I need to search where that was (Mark, I might
> misremember, but wasn't it you who posted it somewhere?) and could work
> towards upstreaming that or some other guide. And don't worry, due to
> the different target audience it would be much shorter text than other
> documents I contributed. ;-)

I don't recall anything specific, though it's plausible I said something
in a thread that was basically just the bit about bisecting between
mainline<->pending-fixes<->-next rather than between -next versions.
You're right that we should have that in the documentation somewhere,
I'll look at sending a patch.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)