New branch for linux-next

New branch for linux-next

[Jan Kara]

Hi Stephen,

can you please include:

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git vfs

into linux-next builds for the coming merge window? It contains patches for
VFS that are already lagging for several months and Al seems to be too busy
with other stuff to pick them up so I'm planning to push them directly to
Linus. But additional test coverage in linux-next would be good. Thanks!

								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

Re: New branch for linux-next

[Stephen Rothwell]

Hi Jan,

On Mon, 26 Sep 2016 12:36:34 +0200 Jan Kara <jack@suse.cz> wrote:
>
> can you please include:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git vfs
> 
> into linux-next builds for the coming merge window? It contains patches for
> VFS that are already lagging for several months and Al seems to be too busy
> with other stuff to pick them up so I'm planning to push them directly to
> Linus. But additional test coverage in linux-next would be good. Thanks!

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