From: Randy Dunlap <rdunlap@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.com>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/3] Remove ext3 filesystem driver
Date: Wed, 15 Jul 2015 08:09:04 -0700 [thread overview]
Message-ID: <55A67790.80802@infradead.org> (raw)
In-Reply-To: <55A676BF.8020903@infradead.org>
On 07/15/15 08:05, Randy Dunlap wrote:
> On 07/15/15 07:18, Theodore Ts'o 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? :-)
>>
>> 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
>
>
> Yes, if someone is going to force us to use ext4, some automation would
> be helpful.
>
> Thanks,
>
Are there any other changes required, e.g., to /etc/fstab ?
btw, this looks like an April 1 joke to me.
--
~Randy
next prev parent reply other threads:[~2015-07-15 15:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 10:26 [PATCH 0/3] Remove ext3 filesystem driver Jan Kara
2015-07-15 10:26 ` [PATCH 1/3] doc: Update doc about journalling layer Jan Kara
2015-07-15 10:26 ` [PATCH 3/3] block: Remove forced page bouncing under IO Jan Kara
2015-07-15 11:02 ` [PATCH 0/3] Remove ext3 filesystem driver Nikolay Borisov
2015-07-15 12:47 ` Jan Kara
2015-07-15 14:18 ` Theodore Ts'o
2015-07-15 15:05 ` Randy Dunlap
2015-07-15 15:09 ` Randy Dunlap [this message]
2015-07-15 15:11 ` Eric Sandeen
2015-07-15 15:14 ` Randy Dunlap
2015-07-15 15:20 ` Austin S Hemmelgarn
2015-07-15 23:23 ` Theodore Ts'o
2015-07-16 8:53 ` Jan Kara
2015-07-15 14:47 ` Jens Axboe
2015-07-15 15:01 ` Joe Perches
2015-07-16 7:27 ` Jan Kara
[not found] ` <1436955987-7305-3-git-send-email-jack@suse.com>
2015-07-15 16:58 ` [PATCH 2/3] fs: " Andrew Morton
2015-07-15 17:35 ` Austin S Hemmelgarn
2015-07-28 21:50 ` Bruce Guenter
2015-07-16 9:41 ` Jan Kara
2015-07-29 12:20 ` [PATCH 0/3] " Konstantin Khlebnikov
2015-07-29 13:49 ` Jan Kara
2015-09-27 7:24 ` Pavel Machek
2015-09-28 17:45 ` Theodore Ts'o
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=55A67790.80802@infradead.org \
--to=rdunlap@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).