Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 19 Sep 2019 20:23:28 +0800
From:   Gao Xiang <gaoxiang25@huawei.com>
To:     Mark Brown <broonie@kernel.org>
CC:     Stephen Rothwell <sfr@canb.auug.org.au>,
        <linux-next@vger.kernel.org>, <linux-erofs@lists.ozlabs.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Chao Yu <yuchao0@huawei.com>, Miao Xie <miaoxie@huawei.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: erofs -next tree inclusion request
Message-ID: <20190919122328.GA82662@architecture4>
References: <20190919120110.GA48697@architecture4>
 <20190919121739.GG3642@sirena.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190919121739.GG3642@sirena.co.uk>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Mark,

On Thu, Sep 19, 2019 at 01:17:39PM +0100, Mark Brown wrote:
> On Thu, Sep 19, 2019 at 08:01:10PM +0800, Gao Xiang wrote:
> 
> > Could you kindly help add the erofs -next tree to linux-next?
> 
> > git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev
> 
> > This can test all erofs patches with the latest linux-next tree
> > and make erofs better...
> 
> That seems like a good idea however since we're in the merge window and 
> the only things that should be being added to -next right now are fixes
> I'll hold off on doing this myself.  Stephen will be back on the 30th
> (just after merge window closes), I'm sure he'll be happy to add the
> tree but in case this gets lost in all the mail from the time he's been
> travelling you might want to remind him after that.
> 
> If you have a separate fixes branch I'd be happy to add that right now.

Thanks for the -fixes information and detailed reminder (I didn't notice
that, sorry...)

I will do a -fix only branch later for urgent and trivial fixes.

For -next, it's okay to wait for Stephen of course :) ...

Thanks,
Gao Xiang