From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:37706 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727041AbeJYTkW (ORCPT ); Thu, 25 Oct 2018 15:40:22 -0400 Date: Thu, 25 Oct 2018 13:08:04 +0200 From: Jan Kara To: Amir Goldstein Cc: Phillip Potter , Al Viro , linux-kernel , linux-fsdevel , Jan Kara Subject: Re: [RFC][PATCH 00/11] common implementation of dirent file types Message-ID: <20181025110804.GG3626@quack2.suse.cz> References: <20181023201952.GA15676@pathfinder> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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 SUSE Labs, CR