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: <2274419.1769795849@warthog.procyon.org.uk>
Date: Fri, 30 Jan 2026 17:57:29 +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:

> Thanks, Mark. David, I see the patches in keys-next were updated just
> a few hours ago. Would it make sense for you to rebase them on top of
> next-20260129? Petr's patch removed the use_signed_attrs variable, so
> we should ensure it's still initialized correctly. Otherwise the
> resolution looks trivial.

Wouldn't that mean having to rebase before sending to Linus?

What's your branch that is being taken into linux-next?

David