linux-kernel - Re: linux-next: duplicate patches in the tip tree

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

Message-ID: <878qpb20bh.ffs@tglx>
Date: Tue, 11 Mar 2025 13:56:02 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Andrew Morton
 <akpm@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Peter
 Zijlstra <peterz@...radead.org>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the tip tree

On Tue, Mar 11 2025 at 22:43, Stephen Rothwell wrote:
> On Tue, 11 Mar 2025 02:02:40 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>> There's presumably a better way of doing this, but it's really the
>> first time it has happened in N years so it isn't obviously worth
>> investing in setting something up.
>
> This is why we have shared stable branches.  If the tip guys have all
> those commits in a branch that they guarantee will not rebase (or be
> rewritten), then you could fetch that branch and merge it into your
> tree somewhere.

tip timers/vdso is stable and won't be rebased. It might get delta fixes
on top, but that should be not a problem.

Andrew, feel free to pull that in.

Thanks,

        tglx