Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754748Ab0D0Phg (ORCPT ); Tue, 27 Apr 2010 11:37:36 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:47552 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753614Ab0D0Phe (ORCPT ); Tue, 27 Apr 2010 11:37:34 -0400 Date: Tue, 27 Apr 2010 08:36:03 -0700 (PDT) From: Linus Torvalds To: John Kacur cc: =?ISO-8859-15?Q?J=F6rn_Engel?= , Arnd Bergmann , lkml , Frederic Weisbecker , Jan Blunck , Thomas Gleixner Subject: Re: [PATCH 1/7] logfs: push down BKL into ioctl function In-Reply-To: Message-ID: References: <1272378265-10909-2-git-send-email-arnd@arndb.de> <20100427145804.GA16794@logfs.org> <201004271705.50499.arnd@arndb.de> <20100427150919.GB16794@logfs.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 23 On Tue, 27 Apr 2010, John Kacur wrote: > > You can ask Linus whether he'll take a convert unlocked_ioctl now or not. Absolutely not. I could imagine merging something like just the bkl_ioctl rename: if it breaks, it won't compile, so there is little risk, and _if_ it helps the next merge window I could merge it early. But it looks like people are trying to avoid it entirely, and there is not a way in *hell* I will take some big and scary "push BKL down" patch that is clearly _not_ 99% mechanical and clearly _can_ introduce major and subtle bugs while compiling. 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/