Add libcrypto trees to linux-next

Add libcrypto trees to linux-next

[Eric Biggers]

Hi Stephen, could you add the following to linux-next:

    Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
    Branches: libcrypto-next and libcrypto-fixes

It should match the CRYPTO LIBRARY entry in MAINTAINERS.

Thanks!

- Eric

Re: Add libcrypto trees to linux-next

[Stephen Rothwell]

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

Hi Eric,

On Thu, 5 Jun 2025 18:12:22 -0700 Eric Biggers <ebiggers@kernel.org> wrote:
>
> Hi Stephen, could you add the following to linux-next:
> 
>     Repo: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
>     Branches: libcrypto-next and libcrypto-fixes
> 
> It should match the CRYPTO LIBRARY entry in MAINTAINERS.

Added from Tuesday (Monday is a public holiday here).

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.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

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