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 v5 06/09] f2fs: use common file type conversion
Date: Thu, 24 Jan 2019 09:27:37 +0000 [thread overview]
Message-ID: <20190124092737.GA25629@pathfinder> (raw)
In-Reply-To: <6f759f75-5906-e499-e86b-a915d714e8c4@huawei.com>
On Wed, Jan 23, 2019 at 02:27:34PM +0800, Chao Yu wrote:
> On 2019/1/21 8:54, Phillip Potter wrote:
> > Deduplicate the f2fs file type conversion implementation and remove
> > F2FS_FT_* definitions - 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>
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> Thanks,
>
Thank you very much for this.
Regards,
Phil
prev parent reply other threads:[~2019-01-24 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 0:54 [RFC][PATCH v5 06/09] f2fs: use common file type conversion Phillip Potter
2019-01-23 6:27 ` Chao Yu
2019-01-24 9:27 ` 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=20190124092737.GA25629@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).