From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: devel@driverdev.osuosl.org, Chao Yu <chao@kernel.org>,
linux-erofs@lists.ozlabs.org, Chao Yu <yuchao0@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, weidu.du@huawei.com,
Fang Wei <fangwei1@huawei.com>, Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH v3 1/2] staging: erofs: add requirements field in superblock
Date: Sun, 16 Jun 2019 09:14:39 +0200 [thread overview]
Message-ID: <20190616071439.GA11880@kroah.com> (raw)
In-Reply-To: <a4d587eb-c4f0-b9e5-7ece-1ac38c2735f3@huawei.com>
On Sun, Jun 16, 2019 at 03:00:38PM +0800, Gao Xiang wrote:
> Hi Greg,
>
> Sorry for annoying... Could you help merge these two fixes? Thanks in advance...
It was only 3 days, please give me at the very least, a week or so for
staging patches.
> decompression inplace optimization needs these two patches and I will integrate
> erofs decompression inplace optimization later for linux-next 5.3, and try to start
> making effort on moving to fs/ directory on kernel 5.4...
You can always send follow-on patches, I apply them in the correct
order. I will get to these next week, thanks.
greg k-h
next prev parent reply other threads:[~2019-06-16 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 2:42 [PATCH v2 1/2] staging: erofs: add requirements field in superblock Gao Xiang
2019-06-11 3:01 ` Chao Yu
2019-06-13 8:35 ` [PATCH v3 " Gao Xiang
[not found] ` <20190615221606.1C12F2183F@mail.kernel.org>
2019-06-16 6:47 ` Gao Xiang
2019-06-16 7:00 ` Gao Xiang
2019-06-16 7:14 ` Greg Kroah-Hartman [this message]
2019-06-16 7:21 ` Gao Xiang
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=20190616071439.GA11880@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chao@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=fangwei1@huawei.com \
--cc=gaoxiang25@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=stable@vger.kernel.org \
--cc=weidu.du@huawei.com \
--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