Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752845AbbGOOSm (ORCPT ); Wed, 15 Jul 2015 10:18:42 -0400 Received: from imap.thunk.org ([74.207.234.97]:42829 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751922AbbGOOSj (ORCPT ); Wed, 15 Jul 2015 10:18:39 -0400 Date: Wed, 15 Jul 2015 10:18:36 -0400 From: "Theodore Ts'o" To: Jan Kara Cc: 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: <20150715141836.GA18400@thunk.org> Mail-Followup-To: Theodore Ts'o , Jan Kara , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, LKML , Andrew Morton , Andreas Dilger , Jens Axboe References: <1436955987-7305-1-git-send-email-jack@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436955987-7305-1-git-send-email-jack@suse.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1398 Lines: 39 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? :-) 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 In any case, since the 2/3 patch didn't hit the list, here's my: Acked-by: Theodore Ts'o For that patch. - Ted -- 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/