mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Gao Xiang" <gaoxiang25@huawei.com>,
	"Chao Yu" <yuchao0@huawei.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: erofs: use explicit unsigned int type
Date: Wed, 12 Sep 2018 00:46:12 +0800	[thread overview]
Message-ID: <1b6fcc86-5b0c-e5b3-15de-63938222213e@kernel.org> (raw)
In-Reply-To: <20180910194114.13314-1-linux@weissschuh.net>

On 2018/9/11 3:41, Thomas Weißschuh wrote:
> Hi Chao,
> 
> On Mon, 2018-09-10T23:59+0800, Chao Yu wrote:
>> [...]
> 
>>>> 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.
> 
> Thank you for clearing this up! And I am sorry for causing you all this work
> for what is essentially a very small style cleanup.
> 
>> 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. :)
> 
> The patch follows.
> 
> Thomas
> 
> 
> Changes since v1:
> 
> * Removed changes that conflicted with
>   [PATCH 1/6] staging: erofs: formatting fix in unzip_vle_lz4.c
> * Added patch description
> 
> Changes since v2:
> 
> * Fixed conflicts with other patchsets
> * Don't introduce new style issues
> 
> Changes since v3:
> 
> * Fixed conflicts with other patchsets
> 
> Note: This patchset should be applied with the "git am --scissors", to
> remove the historic information and this note.
> 
> -- >8 --
> 
> Fix coding style issue "Prefer 'unsigned int' to bare use of 'unsigned'"
> detected by checkpatch.pl.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

  reply	other threads:[~2018-09-11 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180830205605.19492-1-linux@weissschuh.net>
2018-09-07 16:39 ` [PATCH v2] " Thomas Weißschuh
2018-09-08  3:28   ` Gao Xiang
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-10  3:56       ` Gao Xiang
2018-09-10 15:59         ` Chao Yu
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-11 16:46             ` Chao Yu [this message]
2018-09-12  6:21             ` Gao Xiang
2018-09-13 16:46               ` Gao Xiang
2018-09-09 18:37     ` [PATCH v3] " Thomas Weißschuh
2018-09-10  8:10       ` Greg Kroah-Hartman
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=1b6fcc86-5b0c-e5b3-15de-63938222213e@kernel.org \
    --to=chao@kernel.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gaoxiang25@huawei.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome