All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Chao Yu <chao@kernel.org>, Chao Yu <yuchao0@huawei.com>,
	<linux-erofs@lists.ozlabs.org>, <devel@driverdev.osuosl.org>,
	<linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: add tree location for staging/erofs
Date: Tue, 11 Sep 2018 00:50:05 +0800	[thread overview]
Message-ID: <e58d6b95-7ea8-63ca-1827-8680e9d4ef99@huawei.com> (raw)
In-Reply-To: <23218dc6-8aba-a4e6-7c18-64380082f747@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 <linux@weissschuh.net>
>>> ---
>>>  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 <gaoxiang25@huawei.com>
>>>  M:	Chao Yu <yuchao0@huawei.com>
>>> +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/
>>>

WARNING: multiple messages have this Message-ID (diff)
From: gaoxiang25@huawei.com (Gao Xiang)
Subject: [PATCH] MAINTAINERS: add tree location for staging/erofs
Date: Tue, 11 Sep 2018 00:50:05 +0800	[thread overview]
Message-ID: <e58d6b95-7ea8-63ca-1827-8680e9d4ef99@huawei.com> (raw)
In-Reply-To: <23218dc6-8aba-a4e6-7c18-64380082f747@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 <linux at weissschuh.net>
>>> ---
>>>  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 <gaoxiang25 at huawei.com>
>>>  M:	Chao Yu <yuchao0 at huawei.com>
>>> +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 at lists.ozlabs.org
>>>  S:	Maintained
>>>  F:	drivers/staging/erofs/
>>>

  reply	other threads:[~2018-09-10 16:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 20:56 [PATCH] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-03  1:53 ` Chao Yu
2018-09-07  8:48   ` Gao Xiang
2018-09-07  9:17     ` Dan Carpenter
2018-09-07 11:01       ` Gao Xiang
2018-09-07 16:39 ` [PATCH v2] " Thomas Weißschuh
2018-09-07 16:39   ` Thomas Weißschuh
2018-09-08  3:28   ` Gao Xiang
2018-09-08  3:28     ` Gao Xiang
2018-09-09 15:16     ` Chao Yu
2018-09-09 15:16       ` Chao Yu
2018-09-09 18:34     ` [PATCH] MAINTAINERS: add tree location for staging/erofs Thomas Weißschuh
2018-09-09 18:34       ` Thomas Weißschuh
2018-09-10  3:56       ` Gao Xiang
2018-09-10  3:56         ` Gao Xiang
2018-09-10 15:59         ` Chao Yu
2018-09-10 15:59           ` Chao Yu
2018-09-10 16:50           ` Gao Xiang [this message]
2018-09-10 16:50             ` Gao Xiang
2018-09-10 19:41           ` [PATCH v4] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-10 19:41             ` Thomas Weißschuh
2018-09-11 16:46             ` Chao Yu
2018-09-11 16:46               ` Chao Yu
2018-09-12  6:21             ` Gao Xiang
2018-09-12  6:21               ` Gao Xiang
2018-09-13 16:46               ` Gao Xiang
2018-09-13 16:46                 ` Gao Xiang
2018-09-09 18:37     ` [PATCH v3] " Thomas Weißschuh
2018-09-09 18:37       ` Thomas Weißschuh
2018-09-10  8:10       ` Greg Kroah-Hartman
2018-09-10  8:10         ` Greg Kroah-Hartman
2018-09-10 19:15         ` Thomas Weißschuh
2018-09-10 19:15           ` Thomas Weißschuh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e58d6b95-7ea8-63ca-1827-8680e9d4ef99@huawei.com \
    --to=gaoxiang25@huawei.com \
    --cc=chao@kernel.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=yuchao0@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.