linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: Boaz Harrosh <ooo@electrozaur.com>
Cc: amir73il@gmail.com, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH v2 05/10] exofs: use common file type conversion
Date: Wed, 24 Oct 2018 14:31:45 +0100	[thread overview]
Message-ID: <20181024133145.GB23398@pathfinder> (raw)
In-Reply-To: <11231c2a-0bb8-5c87-a65c-4fc7ff47f866@electrozaur.com>

On Wed, Oct 24, 2018 at 02:56:58PM +0300, Boaz Harrosh wrote:
> On 23/10/18 23:19, Phillip Potter wrote:
> > Deduplicate the exofs file type conversion implementation.
> > 
> > Original patch by Amir Goldstein.
> > 
> > v2:
> > - This version does not remove EXOFS_FT_x enum from fs/exofs/common.h,
> >   as these values are now used in compile-time checks added by
> >   Phillip Potter to make sure they remain the same as FT_x values
> > 
> > v1:
> > - Initial implementation
> > 
> > Signed-off-by: Phillip Potter <phil@philpotter.co.uk>
> 
> Yes thank you, totally
> 
> ACK-by: Boaz Harrosh <ooo@electrozaur.com>
>

Dear Boaz,

Thank you for this. I am publishing a new series with a minor comment fix
included for this patch (formatting to 80-lines properly). I shall keep
your ACK-by line in the new patch.

Regards,
Phil

      reply	other threads:[~2018-10-24 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 20:19 [RFC][PATCH v2 05/10] exofs: use common file type conversion Phillip Potter
2018-10-24 11:56 ` Boaz Harrosh
2018-10-24 13:31   ` 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=20181024133145.GB23398@pathfinder \
    --to=phil@philpotter.co.uk \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ooo@electrozaur.com \
    --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;
as well as URLs for NNTP newsgroup(s).