From: Arnd Bergmann Subject: Re: [PATCH 0/5] ext2: Preparation to remove BKL Date: Tue, 13 Apr 2010 11:31:54 +0200 Message-ID: <201004131131.54650.arnd@arndb.de> References: <1271104905-8804-1-git-send-email-jblunck@suse.de> <20100412210127.GE8285@nowhere> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Jan Blunck , Jan Kara , tytso@mit.edu, "Linux-Kernel Mailinglist" , linux-ext4@vger.kernel.org To: Frederic Weisbecker Return-path: Received: from moutng.kundenserver.de ([212.227.17.8]:50018 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752065Ab0DMJb6 (ORCPT ); Tue, 13 Apr 2010 05:31:58 -0400 In-Reply-To: <20100412210127.GE8285@nowhere> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Monday 12 April 2010, Frederic Weisbecker wrote: > It looks like this is all about .35 material. > > This is going to be hard to have a separate tree to pushdown/remove > the bkl in the mount path if it depends on the ext2 tree. The pushdown can be in a separate tree that can be merged independently, just the final patch removing it in do_new_mount needs to wait for everything else to get merged first. We have some other patches, in particular the one that makes CONFIG_BKL modular that have to wait for other patches and should probably just be applied separately rather than merged from a bisectable git tree. Arnd