Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758735Ab0KRXlg (ORCPT ); Thu, 18 Nov 2010 18:41:36 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:48932 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755887Ab0KRXlf convert rfc822-to-8bit (ORCPT ); Thu, 18 Nov 2010 18:41:35 -0500 MIME-Version: 1.0 In-Reply-To: <20101118233439.GB5004@quack.suse.cz> References: <1290007619-5787-1-git-send-email-arnd@arndb.de> <20101118233439.GB5004@quack.suse.cz> From: Linus Torvalds Date: Thu, 18 Nov 2010 15:40:56 -0800 Message-ID: Subject: Re: [PATCH 0/7] BKL removal follow-up To: Jan Kara Cc: Arnd Bergmann , linux-kernel@vger.kernel.org, Nathan Laredo , Greg Kroah-Hartman , Dave Airlie , dri-devel@lists.freedesktop.org, "J. Bruce Fields" , linux-nfs@vger.kernel.org, Alessio Igor Bogani Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 860 Lines: 19 On Thu, Nov 18, 2010 at 3:34 PM, Jan Kara wrote: > > ?Just for info, UDF BKL removal patches seem to work fine but I want to > give them some final SMP testing on Monday before pushing them to -next. > I'm not sure how much people hurry with disabling the lock so if I should > push them ASAP or whether the next merge window is fine... I don't think I can reasonably do it in 37, we're late enough in the -rc series. So UDF and really saying 'n' to BKL by default will have to be for the next merge window. I hate to do it, but I'd be too nervous about it any other way. Linus -- 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/