linux-kernel - Re: Please add fscrypt.git to linux-next

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]

Date:   Wed, 4 Jan 2017 22:51:01 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Theodore Ts'o <tytso@....edu>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Please add fscrypt.git to linux-next

Hi Ted,

On Tue, 3 Jan 2017 23:44:24 -0500 Theodore Ts'o <tytso@....edu> wrote:
>
> Could you please add:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git  master
> 
> To the linux-next tree?  I was previously feeding fscrypt changes by
> merging them into the ext4.git dev branch, but it will make life
> simpler if we have a separate git tree for it.
> 
> Linus has already accepted a pull request from the for-stable branch
> of fscrypt.git.  I plan to send a separate pull request for the master
> branch of fscrypt.git during the next merge window.

Added from tomorrow.  Should I add the for-stable branch as well (as a
bug fixes tree)?

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@...b.auug.org.au