New branch for linux-next
Jan Kara
reviewerHi 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
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Hi Jan,
Quoted 9 lines · On Mon, 26 Sep 2016 12:36:34 +0200 Jan Kara <[email protected]> wrote:
can you please include:
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.gitvfsinto 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.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected]