From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A44C3C3A5A6 for ; Thu, 19 Sep 2019 12:29:03 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2C3E321D56 for ; Thu, 19 Sep 2019 12:29:02 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2C3E321D56 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 46Yx3c0hfgzF27d for ; Thu, 19 Sep 2019 22:29:00 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=huawei.com (client-ip=45.249.212.255; helo=huawei.com; envelope-from=gaoxiang25@huawei.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=huawei.com Received: from huawei.com (szxga08-in.huawei.com [45.249.212.255]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 46Ywyh3Q56zF377 for ; Thu, 19 Sep 2019 22:24:42 +1000 (AEST) Received: from DGGEMM405-HUB.china.huawei.com (unknown [172.30.72.57]) by Forcepoint Email with ESMTP id 66228DBD6BA5B586BD93; Thu, 19 Sep 2019 20:24:38 +0800 (CST) Received: from dggeme762-chm.china.huawei.com (10.3.19.108) by DGGEMM405-HUB.china.huawei.com (10.3.20.213) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 19 Sep 2019 20:24:38 +0800 Received: from architecture4 (10.140.130.215) by dggeme762-chm.china.huawei.com (10.3.19.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Thu, 19 Sep 2019 20:24:37 +0800 Date: Thu, 19 Sep 2019 20:23:28 +0800 From: Gao Xiang To: Mark Brown 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) X-Originating-IP: [10.140.130.215] X-ClientProxiedBy: dggeme714-chm.china.huawei.com (10.1.199.110) To dggeme762-chm.china.huawei.com (10.3.19.108) X-CFilter-Loop: Reflected X-BeenThere: linux-erofs@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development of Linux EROFS file system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stephen Rothwell , linux-erofs@lists.ozlabs.org, LKML , Linus Torvalds , linux-next@vger.kernel.org, Greg Kroah-Hartman , Miao Xie Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" 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