From: Phillip Potter <phil@philpotter.co.uk>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
amir73il@gmail.com, viro@zeniv.linux.org.uk,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [RFC][PATCH v3 08/10] f2fs: use common file type conversion
Date: Mon, 29 Oct 2018 11:04:59 +0000 [thread overview]
Message-ID: <20181029110459.GA13236@pathfinder> (raw)
In-Reply-To: <d9979cf6-899d-b264-35df-d765e6f0adba@huawei.com>
On Mon, Oct 29, 2018 at 06:35:03PM +0800, Chao Yu wrote:
> On 2018/10/27 8:53, Phillip Potter wrote:
> > Deduplicate the f2fs file type conversion implementation - file systems
> > that use the same file types as defined by POSIX do not need to define
> > their own versions and can use the common helper functions decared in
> > fs_types.h and implemented in fs_types.c
> >
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > Signed-off-by: Phillip Potter <phil@philpotter.co.uk>
>
> Acked-by: Chao Yu <yuchao0@huawei.com>
>
> Thanks,
>
Thanks for this, appreciate it :-)
Regards,
Phil
prev parent reply other threads:[~2018-10-29 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 0:53 [RFC][PATCH v3 08/10] f2fs: use common file type conversion Phillip Potter
2018-10-29 10:35 ` Chao Yu
2018-10-29 11:04 ` Phillip Potter [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=20181029110459.GA13236@pathfinder \
--to=phil@philpotter.co.uk \
--cc=amir73il@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).