Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2971904imm; Mon, 10 Sep 2018 09:03:30 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbcTWPpUi+WprLt02ZpyGYTagGxLX52qXgPd6GpWSQtvQ9spOs4nQD7Z8t5pPMcqONbuTj8 X-Received: by 2002:a17:902:7b97:: with SMTP id w23-v6mr22785892pll.66.1536595410130; Mon, 10 Sep 2018 09:03:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536595410; cv=none; d=google.com; s=arc-20160816; b=pQ2CntdFSGO06OxibZpdJ15jFZl4U6pJRZ2Z6GYHheCzxQAUu9pHCvYnP2fLg0rmUd W2iXUNiKFcdozd4nLIrAyGZ5TfCxe1uhlY5EfvNXuZjsfDyHl/hiGO/mGkQ9ZRoyyuth QDjo6FCuU6XfbOGsYMZvDOVYfZqKmT9s29nLL/DJY3bfx0st7cqvKNLbsLrTwCZLXArJ wPIwTCuuu/cq77tXxxSgg1yN0S2SEziuZhTaw1rBr6kH2L1CxLdeL9J8iWpBvlKATKQ3 raKUTHfetnSfVxSGaKittRSRtqRUPpn3Mnxsd+X7N0+zCssDcN6fHHkFQ7cugRgjnv9d kJMg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=J8vh0rTGjkAMstJYoGmhv0RNx6d5U1ZVykjCPtyl/iY=; b=bnAnQmPZQi4K3A+Ghv69zgVVh//EpSBPTiYJ75UHunc76DvkEFK47YU3QM0jwIK2GD evkk1KLdw25IaBLjMrLcyxtqpW2Y7KzqTeB6setkdKjpcVdqX3yirVsSkee91Zv67Mn6 ZLh4Up3M4DYFC0WF/ST3UCTneizWs+qRNtFg0gnsidnbsgLHKuVh3XswhxYccIIeT6Qf EUcbJ/6YklOW+J+sE1i0CFSQaMbRcqqtHOgXXjfVwjdWeNdtNPekKDdDpVgVB2yJ3jGs hKho4DjxUvkTFue1hKpB9p/P2fY/ERMyEbYLMzPqikyA105DLrFkSIaZnGA1rPcnxBFS NRuw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=HNWE12pP; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y27-v6si18039139pgl.479.2018.09.10.09.03.14; Mon, 10 Sep 2018 09:03:30 -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; dkim=pass header.i=@kernel.org header.s=default header.b=HNWE12pP; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728462AbeIJUys (ORCPT + 99 others); Mon, 10 Sep 2018 16:54:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:49718 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727777AbeIJUys (ORCPT ); Mon, 10 Sep 2018 16:54:48 -0400 Received: from [192.168.0.101] (unknown [49.77.179.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 659AA20865; Mon, 10 Sep 2018 16:00:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1536595203; bh=3cZhwFVPU1w4eSrTiV0BzCIvAYgTam4YnTRwJ2jqioY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=HNWE12pPfFY72POwG6QI/7BE51M0Hqy+HzfNR86aO3H+MA6WTLQGI+jPAszAykAqg wzONGg/YADvYu41J3Joyv9ovMbFmJ7eLO9RR/CUlA+YNdnT/d3SJQXi6uKXvjSvslf kZG/SXrQ9TqNsSyYDiS3oG3d43laoBxXvhAJcpwY= Subject: Re: [PATCH] MAINTAINERS: add tree location for staging/erofs To: Gao Xiang , =?UTF-8?Q?Thomas_Wei=c3=9fschuh?= , Chao Yu , linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman References: <5c44a63b-041d-1fce-0748-53c0b44f5983@huawei.com> <20180909183432.9752-1-linux@weissschuh.net> <2dc6fb51-dfd6-3509-8833-c889193dd4a9@huawei.com> From: Chao Yu Message-ID: <23218dc6-8aba-a4e6-7c18-64380082f747@kernel.org> Date: Mon, 10 Sep 2018 23:59:58 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <2dc6fb51-dfd6-3509-8833-c889193dd4a9@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 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. :) 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/ >>