[f2fs-dev] Add fsverity tree to linux-next

[f2fs-dev] Add fsverity tree to linux-next

[Eric Biggers]

Hi Stephen,

Can you please add the fsverity tree to linux-next?

        https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git#fsverity

This branch contains the latest fs-verity patches
(https://lore.kernel.org/linux-fsdevel/20190722165101.12840-1-ebiggers@kernel.org/T/#u).
We are planning a pull request for 5.4.

Please use as contacts:

        Eric Biggers <ebiggers@kernel.org>
        Theodore Y. Ts'o <tytso@mit.edu>

Thanks!

- Eric


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Add fsverity tree to linux-next

[Eric Biggers]

Hi Stephen,

Can you please add the fsverity tree to linux-next?

        https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git#fsverity

This branch contains the latest fs-verity patches
(https://lore.kernel.org/linux-fsdevel/20190722165101.12840-1-ebiggers@kernel.org/T/#u).
We are planning a pull request for 5.4.

Please use as contacts:

        Eric Biggers <ebiggers@kernel.org>
        Theodore Y. Ts'o <tytso@mit.edu>

Thanks!

- Eric

Re: Add fsverity tree to linux-next

[Stephen Rothwell]

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

Hi Eric,

On Sun, 28 Jul 2019 20:12:26 -0700 Eric Biggers <ebiggers@kernel.org> wrote:
>
> Can you please add the fsverity tree to linux-next?
> 
>         https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git#fsverity
> 
> This branch contains the latest fs-verity patches
> (https://lore.kernel.org/linux-fsdevel/20190722165101.12840-1-ebiggers@kernel.org/T/#u).
> We are planning a pull request for 5.4.
> 
> Please use as contacts:
> 
>         Eric Biggers <ebiggers@kernel.org>
>         Theodore Y. Ts'o <tytso@mit.edu>

Added from tomorrow.

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 --]