From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lino Sanfilippo Subject: Re: [PATCH 0/9] fsnotify: change locking order Date: Tue, 27 Mar 2012 00:51:22 +0200 Message-ID: <20120326225122.GA3296@Neptun> References: <1308065393-29463-1-git-send-email-LinoSanfilippo@gmx.de> <4E370EBE.3050100@redhat.com> <20110811231331.GB5735@uranus.sol> <87fwd3glak.fsf@camandro.org> <1332269899.3178.3.camel@localhost> <87ty1bli0o.fsf@camandro.org> <1332774776.3290.10.camel@localhost> <20120326152742.GA3124@zeus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: eparis@redhat.com, viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org To: Luis Henriques Return-path: Received: from mailout-de.gmx.net ([213.165.64.23]:42826 "HELO mailout-de.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752408Ab2CZWv0 (ORCPT ); Mon, 26 Mar 2012 18:51:26 -0400 Content-Disposition: inline In-Reply-To: <20120326152742.GA3124@zeus> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Mar 26, 2012 at 04:27:42PM +0100, Luis Henriques wrote: > > No problem, and thank you for the update. I guess this is the sort of > patches that actually requires a good amount of testing on -next, so > it makes sense to wait for next window. > I totally agree. Better to have this in linux-next for a while and make sure that no nasty side effects have been introduced.