erofs -next tree inclusion request
Gao Xiang
hsiangkao at aol.com
Mon Sep 30 23:32:22 AEST 2019
Hi Stephen,
On Mon, Sep 30, 2019 at 11:14:39PM +1000, Stephen Rothwell wrote:
> 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).
That is ok, and thanks for your great work.
>
> Which address(es) should I use as your contact address(es)?
I think xiang at kernel.org is preferred since it can always redirect
to my workable email address.
>
> 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.
Thanks for the kind reminder :)
Thanks,
Gao Xiang
More information about the Linux-erofs
mailing list