From: Chao Yu <yuchao0@huawei.com>
To: Sahitya Tummala <stummala@codeaurora.org>
Cc: sunqiuyang <sunqiuyang@huawei.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v6 1/1] f2fs: ioctl for removing a range from F2FS
Date: Fri, 24 May 2019 11:28:01 +0800 [thread overview]
Message-ID: <d298c4a5-4ba7-df8c-5bbe-74ce4ce9604e@huawei.com> (raw)
In-Reply-To: <20190524030958.GB10043@codeaurora.org>
On 2019/5/24 11:09, Sahitya Tummala wrote:
> I am okay with merging.
Thank you, it looks Qiuyang has confirmed before v2. :)
Thanks,
next prev parent reply other threads:[~2019-05-24 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 1:55 [PATCH v6 1/1] f2fs: ioctl for removing a range from F2FS sunqiuyang
2019-05-24 2:32 ` Chao Yu
2019-05-24 3:09 ` Sahitya Tummala
2019-05-24 3:28 ` Chao Yu [this message]
2019-05-30 16:06 ` Jaegeuk Kim
2019-05-31 1:48 ` Chao Yu
2019-06-03 16:23 ` Jaegeuk Kim
2019-06-04 1:43 ` Chao Yu
2019-06-04 10:25 ` sunqiuyang
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=d298c4a5-4ba7-df8c-5bbe-74ce4ce9604e@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=sunqiuyang@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;
as well as URLs for NNTP newsgroup(s).