erofs -next tree inclusion request
Stephen Rothwell
sfr at canb.auug.org.au
Mon Sep 30 23:14:39 AEST 2019
Hi Gao,
On Thu, 19 Sep 2019 22:37:22 +0800 Gao Xiang <hsiangkao at aol.com> wrote:
>
> The fixes only -fixes branch is
> git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
I have added this from tomorrow (sorry for the drop out today).
Which address(es) should I use as your contact address(es)?
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 at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ozlabs.org/pipermail/linux-erofs/attachments/20190930/94105c17/attachment.sig>
More information about the Linux-erofs
mailing list