All of lore.kernel.org
 help / color / mirror / Atom feed
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: [RFC][PATCH v3 10/10] btrfs: use common file type conversion
Date: Wed, 31 Oct 2018 16:45:02 +0100	[thread overview]
Message-ID: <20181031154501.GI9136@suse.cz> (raw)
In-Reply-To: <20181031092231.GC19486@pathfinder>

On Wed, Oct 31, 2018 at 09:22:31AM +0000, Phillip Potter wrote:
> Thanks for this - are you happy for me to move the compile-time tests as per
> Amir's suggestion?

Yes that's ok.

      reply	other threads:[~2018-10-31 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27  0:53 [RFC][PATCH v3 00/10] common implementation of dirent file types Phillip Potter
2018-10-27  0:53 ` [RFC][PATCH v3 10/10] btrfs: use common file type conversion Phillip Potter
2018-10-30 19:03   ` David Sterba
2018-10-31  9:22     ` Phillip Potter
2018-10-31 15:45       ` David Sterba [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=20181031154501.GI9136@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.