Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3027450imm; Mon, 10 Sep 2018 09:52:09 -0700 (PDT) X-Google-Smtp-Source: ANB0VdafPq/L/kWiXuQa9eNe95qUrf0jSEAwh+TkEula3/WdTzYPUmzA4rGa73zq1FGIHctRoh4Q X-Received: by 2002:a63:5706:: with SMTP id l6-v6mr24356761pgb.118.1536598329922; Mon, 10 Sep 2018 09:52:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536598329; cv=none; d=google.com; s=arc-20160816; b=X6xuMduNL5BvtY/t6C17EA/wYWPGXZfIrQ16o/l5hkRxIOvstRYSk8C2kHsWuA5TvG oil7/+DaB+oOCBBJliEdcoHZvjCdukhrsri2AnCWL99nxwrTwuAN2R+pNhZDrzULJOcH C8jZ9AcXOBs//LIYpHZkUsO3hgdR7pLgm2tHSB4HJXwl5f/CRq7p0T2439hV5YG1LsVn bsc1vXoZE9IWEDzj8meejeEI2HK/4UnTUHloyNAFmzUQI47+klLcDUaey/snD/M04QYB 7vXXtMry44jK8ggqOCJUKNQTtyyILq3j5M9hrynd4b9Eat3KY3nylBcddSIniI7YX9s5 TsQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=i47JgQVZczEajXHe+/oMCaVhlPjhZAXXKCWu5RIMuiA=; b=IoIJCdCxu8FJ7ZXn19rEd5Ps3XaogUM0XiePS8qmkroJDwAF8/m/KF/eOb2+UuIIW4 FheXyIOUaJJLfD/5gdjsMp6BDNIi63rk3ioxcgi/T+N9luviIc0hKFmOPH6j08U9rbXZ hClURpRYO9NUmlvwbwv1MdhizKEzWmFFr1qSIJ/kqJ9C0T1x9ZYRD+KiSPqz69E+/t87 5494a52TY6p965G2kg2fi8DyeHHGIrXhi7Ze1QgRxUlJkxaZOpucRGhWknT9YBY8+I9k ORRwJl09BYydOkvqE4bFXYOYWKY/h+urNn5VHZWOMtBMySy+3no5wiSBAyhmAVU1XJbw /P3w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w66-v6si18580852pfi.88.2018.09.10.09.51.54; Mon, 10 Sep 2018 09:52:09 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728818AbeIJVpW (ORCPT + 99 others); Mon, 10 Sep 2018 17:45:22 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:11679 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727772AbeIJVpW (ORCPT ); Mon, 10 Sep 2018 17:45:22 -0400 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 74F99A42077C2; Tue, 11 Sep 2018 00:50:15 +0800 (CST) Received: from [10.151.23.176] (10.151.23.176) by smtp.huawei.com (10.3.19.205) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 11 Sep 2018 00:50:06 +0800 Subject: Re: [PATCH] MAINTAINERS: add tree location for staging/erofs To: =?UTF-8?Q?Thomas_Wei=c3=9fschuh?= CC: Chao Yu , Chao Yu , , , , Greg Kroah-Hartman References: <5c44a63b-041d-1fce-0748-53c0b44f5983@huawei.com> <20180909183432.9752-1-linux@weissschuh.net> <2dc6fb51-dfd6-3509-8833-c889193dd4a9@huawei.com> <23218dc6-8aba-a4e6-7c18-64380082f747@kernel.org> From: Gao Xiang Message-ID: Date: Tue, 11 Sep 2018 00:50:05 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <23218dc6-8aba-a4e6-7c18-64380082f747@kernel.org> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.151.23.176] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, On 2018/9/10 23:59, Chao Yu wrote: > On 2018/9/10 11:56, Gao Xiang wrote: >> >> >> On 2018/9/10 2:34, Thomas Weißschuh wrote: >>> Hi Chao, hi Gao, >>> >>> On Sun, 2018-09-09T23:16+0800, Chao Yu wrote: >>>> Hi Thomas, >>>> >>>> On 2018/9/8 11:28, Gao Xiang wrote: >>>>> Hi Thomas, >>>>> >>>>> Thanks for your new patch. >>>>> >>>>> It seems that this patch also introduces 2 new 'WARNING: line over 80 characters', >>>>> could you please fix it in the patch? >>> >>> @Chao,Gao: For some reason there seems to be a problem when receiving mails >>> from you. The one I received now was the first one from you that reached me >>> directly. Before I only got your messages in the quotes from Dan and now in the >>> quotes from the mail I am responding to. >>> (I will try to investigate the reason for this) >>> >>> Sorry for my slow responses before. >>> >>>> It will be better to fix that. >>> >>> A new patch will shortly follow. >>> >>>> Some reviewed cleanup patches are merged before this patch, then I failed to add >>>> this one, so could you rebase on top of erofs dev branch in below link: >>>> >>>> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=erofs >>> >>> I was not aware of this tree and worked off of staging / next. >>> A patch is attached to this message that adds the tree to the MAINTAINERS file. >> >> Hi Chao, >> >> I think this tree has some PREVIEW patches which preview in linux-erofs mailing list only and >> doesn't send to staging mailing list and LKML, >> >> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=erofs >> >> so erofs tree is actually Greg's staging tree. > > Thomas, > > I confirmed that erofs git repository for linux upstream is Greg's staging tree. > > Let me explain, in order to avoid sending buggy or preview patch, Xiang and me > plan to review patches in erofs mailing list first, and then cache reviewed > patches in my git tree before sending them to Greg and staging mailing list. > > Based on that, I'm trying to serialize all erofs patches, expecting that can > help those patches sent to staging mailing list can be merged by Greg with > lesser conflict. But I made a mistake that my erofs branch has merged some > pending patches, result in failing to merge yours, that mislead me to ask you to > rebase the code, sorry about that. As Chao's said, we keep on fetching the latest Greg's staging tree and develop , preview, and test new erofs features and bugfix based on it. For the cleanup patches, it could be better directly based on Greg's upstream staging tree. We will then rebase our developping code on your work. :) > > Now I can confirm that your v2 patch can apply on Greg's staging-next, so fixing > warning reported by checkpatch.pl on your v2 patch is enough. :) Yes, we are sorry about that. could you please send v4 patch which follows Greg's and Chao's suggestions? Thanks, Gao Xiang > > Thanks, > >> >>> >>> -- >8 -- >>> >>> Currently this location is not documented. >>> >>> Signed-off-by: Thomas Weißschuh >>> --- >>> MAINTAINERS | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/MAINTAINERS b/MAINTAINERS >>> index a5b256b25905..9087e0b74821 100644 >>> --- a/MAINTAINERS >>> +++ b/MAINTAINERS >>> @@ -13747,6 +13747,7 @@ F: drivers/staging/comedi/ >>> STAGING - EROFS FILE SYSTEM >>> M: Gao Xiang >>> M: Chao Yu >>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git erofs >> >> Hi Thomas, >> nope, the erofs tree is actually the same as staging tree, so any patch should be based >> on Greg's upstream tree. >> >> Thanks, >> Gao Xiang >> >>> L: linux-erofs@lists.ozlabs.org >>> S: Maintained >>> F: drivers/staging/erofs/ >>>