From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Phillip Potter <phil@philpotter.co.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [RFC][PATCH 00/11] common implementation of dirent file types
Date: Thu, 25 Oct 2018 13:08:04 +0200 [thread overview]
Message-ID: <20181025110804.GG3626@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxgFdquNqcRXETriSvwc24DDQbmu218WFv-a5K3k0nuu7Q@mail.gmail.com>
On Wed 24-10-18 09:43:21, Amir Goldstein wrote:
> Once all comments are addressed and assuming no objections, you have
> two possible ways forward:
>
> 1. Wait for VFS maintainer to take the common code and patches ACKed
> by individual maintainers (Al practically maintains some of the small fs
> himself). Al's backlog is long, so this may be a long wait.
>
> 2. Ask a filesystem maintainer to carry the common patch along with his
> specific fs patch through his tree and let other maintainers apply the patch
> at their own will on the following development cycle.
> The ext2 tree would be a good candidate for such a move, if Jan accepts
> this change, considering that all other fs copied the buggy code from ext2.
I can take these patches through my tree if Al takes too long to respond
(but he apparently already had a look at the patches which is a good sign
;) and if patches are reviewed by respective fs maintainers.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2018-10-25 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 20:19 [RFC][PATCH 00/11] common implementation of dirent file types Phillip Potter
2018-10-23 21:17 ` [RFC][PATCH v2 10/10] btrfs: use common file type conversion Phillip Potter
2018-10-24 10:11 ` David Sterba
2018-10-24 13:28 ` Phillip Potter
2018-10-24 6:43 ` [RFC][PATCH 00/11] common implementation of dirent file types Amir Goldstein
2018-10-25 11:08 ` Jan Kara [this message]
2018-10-25 12:48 ` Phillip Potter
-- strict thread matches above, loose matches on Subject: below --
2016-12-19 20:10 Amir Goldstein
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=20181025110804.GG3626@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.