linux-kernel - Re: linux-next: manual merge of the keys-next tree with the modules 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2281244.1769810219@warthog.procyon.org.uk>
Date: Fri, 30 Jan 2026 21:56:59 +0000
From: David Howells <dhowells@...hat.com>
To: Sami Tolvanen <samitolvanen@...gle.com>
Cc: dhowells@...hat.com, Mark Brown <broonie@...nel.org>,
    Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
    Linux Next Mailing List <linux-next@...r.kernel.org>,
    Petr Pavlu <petr.pavlu@...e.com>
Subject: Re: linux-next: manual merge of the keys-next tree with the modules tree

Sami Tolvanen <samitolvanen@...gle.com> wrote:

> > Wouldn't that mean having to rebase before sending to Linus?
> 
> Do you plan to send these to Linus for 7.0-rc1?

Yes, hopefully.

> The patches already depend on libcrypto-next landing first, right?

Yes - if that was the only thing, I'd just ask Linus to pull them after that.

> If the patches were last rebased 6h ago, I'm not sure if rebasing them on
> top of modules-next would significantly affect the linux-next soak time, but
> I'm fine either way.

Rebasing on modules-next wouldn't work unless modules-next has Eric's branch
merged in for the ML-DSA bits.  I could maybe merge the two and rebase on
that, but I think Linus isn't keen on that.

David