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: <nycvar.YFH.7.76.2410252303270.20286@cbobk.fhfr.pm>
Date: Fri, 25 Oct 2024 23:04:41 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
cc: Christoph Hellwig <hch@...radead.org>, 
    Geert Uytterhoeven <geert@...ux-m68k.org>, 
    Guenter Roeck <linux@...ck-us.net>, Michael Ellerman <mpe@...erman.id.au>, 
    Kees Cook <kees@...nel.org>, Sasha Levin <sashal@...nel.org>, 
    torvalds@...ux-foundation.org, ksummit@...ts.linux.dev, 
    linux-kernel@...r.kernel.org
Subject: Re: linus-next: improving functional testing for to-be-merged pull
 requests

On Thu, 24 Oct 2024, Steven Rostedt wrote:

> So basically, all I need to do to satisfy your request is to add fixes
> branch that I push to that is pushed after it passes my tests (and not
> the urgent branch that is still being tested and may have bugs) and
> then have that be added to linux-next?

That is one option.

Alternatively do what I have been doing since ever: I have a couple of 
'for-N+1/topic' branches, and then I have one 'for-N/fixes' branch. All of 
them get automerged into 'for-next' branch which Stephen is pulling. Works 
like a charm.

-- 
Jiri Kosina
SUSE Labs