Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754687AbbGPJsy (ORCPT ); Thu, 16 Jul 2015 05:48:54 -0400 Received: from cantor2.suse.de ([195.135.220.15]:53844 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753692AbbGPJsw (ORCPT ); Thu, 16 Jul 2015 05:48:52 -0400 Date: Thu, 16 Jul 2015 10:53:47 +0200 From: Jan Kara To: "Theodore Ts'o" Cc: Jan Kara , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, LKML , Andrew Morton , Andreas Dilger , Jens Axboe Subject: Re: [PATCH 0/3] Remove ext3 filesystem driver Message-ID: <20150716085347.GG22847@quack.suse.cz> References: <1436955987-7305-1-git-send-email-jack@suse.com> <20150715141836.GA18400@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150715141836.GA18400@thunk.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1871 Lines: 50 On Wed 15-07-15 10:18:36, Ted Tso wrote: > On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote: > > > > so I have created this patch set which removes ext3 driver (and some related support > > code) from the kernel. See changelog of patch 2/3 for more details. If noone objects, > > I will queue the series in my tree for the next merge window. > > > > Jens, are you OK with me merging patch 3/3 or do you want me to send it to you once > > the first two patches get merged? > > > > Ted, this also touches ext4 driver so that it always handles ext3 filesystems so ack > > from you would be nice. > > Got tired of maintaining ext3, eh? :-) Not really. Maintaining ext3 has been pretty low-effort in last years. But the releasepage trouble has made me reconsider whether it's worth keeping ext3 codebase and I just came to conclusion that it may be the right time to drop it. > As a minor nit, I wonder if it's worth while to put in some hackery in > fs/Kconfig so that if someone only has CONFIG_FS_EXT3 defined, but not > CONFIG_FS_EXT4 defined, that it will automatically enable > CONFIG_FS_EXT4 instead? Otherwise someone upgrading their kernel > might accidentally end up getting a non-functional kernel. > > i.e., something like this? (not tested!) > > config FS_EXT3 > def_bool n > select FS_EXT4 Good point. Will add something like this, although the config will have to have some prompt for this to work... > In any case, since the 2/3 patch didn't hit the list, here's my: > > Acked-by: Theodore Ts'o Thanks. Honza -- Jan Kara SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/