From: David Sterba <dsterba@suse.cz>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: clm@fb.com, jbacik@fb.com, amir73il@gmail.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v6 07/07] btrfs: use common file type conversion
Date: Wed, 27 Mar 2019 00:55:39 +0100 [thread overview]
Message-ID: <20190326235539.GX10640@suse.cz> (raw)
In-Reply-To: <20190326213934.GA20882@pathfinder>
On Tue, Mar 26, 2019 at 09:39:34PM +0000, Phillip Potter wrote:
> Deduplicate the btrfs 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
>
> Common implementation can be found via commit:
> bbe7449e2599 "fs: common implementation of file type"
Now that the prerequisite patch is in master, I can pick the btrfs
specific part. Thanks.
next prev parent reply other threads:[~2019-03-27 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 21:39 [PATCH v6 07/07] btrfs: use common file type conversion Phillip Potter
2019-03-26 23:55 ` David Sterba [this message]
2019-03-27 0:22 ` Phillip Potter
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=20190326235539.GX10640@suse.cz \
--to=dsterba@suse.cz \
--cc=amir73il@gmail.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=phil@philpotter.co.uk \
--cc=viro@zeniv.linux.org.uk \
/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