Pick up keys-next branch for linux-next?

Pick up keys-next branch for linux-next?

[David Howells]

Hi Stephen, Mark,

Can you pick up my keys-next branch for linux-next please?  It can be found at:

	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/
	keys-next

Note that it's based on part of Eric Bigger's libcrypto/libcrypto-next branch
which I believe you already have in order to get ML-DSA support.

Thanks,
David

Re: Pick up keys-next branch for linux-next?

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

On Fri, Jan 30, 2026 at 12:17:28PM +0000, David Howells wrote:

> Can you pick up my keys-next branch for linux-next please?  It can be found at:

> 	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/
> 	keys-next

> Note that it's based on part of Eric Bigger's libcrypto/libcrypto-next branch
> which I believe you already have in order to get ML-DSA support.

I'll add this from today, called "keys-next", with you as the contact -
anyone else?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]