From: yuchao0@huawei.com (Chao Yu)
Subject: [PATCH v4 0/3] staging: erofs: option validation for remount and some code cleanups
Date: Thu, 20 Sep 2018 09:42:36 +0800 [thread overview]
Message-ID: <36255aa8-8654-891a-ee89-204760edba23@huawei.com> (raw)
In-Reply-To: <ebd19146-a465-e237-c0ef-8147a0b8726f@gmx.com>
On 2018/9/20 7:34, cgxu519 wrote:
> On 9/19/18 11:22 PM, Gao Xiang wrote:
>> Hi Chengguang,
>>
>> On 2018/9/19 22:53, Chengguang Xu wrote:
>>> Hi Greg, Xiang
>>>
>>> I rebased code on latest erofs-master branch and that branch
>>> has already merged the first patch in my previous patchset,
>>> so this time I only post rest 3 patches.
>> Great, at the most time Chao's erofs-master is the same as Greg's
>> staging tree (currently it is), but I personally think all patches
>> could be better directly based on the final staging tree if these
>> patches has no real/effective dependency with some submitted patches
>> but haven't been applied by Greg (p.s. it should be avoided as
>> much as possible because community guys could find something
>> important like the yesterday patches).
>>
>> Once again, the detail information of branches is described in
>> https://lists.ozlabs.org/listinfo/linux-erofs/
Yeah, I can confirm that's all true. :)
>>
>> I have nothing more to say, good luck :)
>>
> Thanks for the guide!
>
> Chengguang
>
> .
>
prev parent reply other threads:[~2018-09-20 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 14:53 [PATCH v4 0/3] staging: erofs: option validation for remount and some code cleanups Chengguang Xu
2018-09-19 14:53 ` [PATCH v4 1/3] staging: erofs: code cleanup for option parsing of fault_injection Chengguang Xu
2018-09-19 14:53 ` [PATCH v4 2/3] staging: erofs: code cleanup for erofs_show_options() Chengguang Xu
2018-09-19 14:53 ` [PATCH v4 3/3] staging: erofs: option validation in remount Chengguang Xu
2018-09-19 15:22 ` [PATCH v4 0/3] staging: erofs: option validation for remount and some code cleanups Gao Xiang
2018-09-19 23:34 ` cgxu519
2018-09-20 1:42 ` Chao Yu [this message]
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=36255aa8-8654-891a-ee89-204760edba23@huawei.com \
--to=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.