From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zach Brown Subject: Re: [Patch] add AOP_TRUNCATED_PAGE, prepend AOP_ to WRITEPAGE_ACTIVATE Date: Fri, 04 Nov 2005 10:31:35 -0800 Message-ID: <436BA907.9080604@oracle.com> References: <43667913.4030401@oracle.com> <20051103124536.0191bea6.akpm@osdl.org> <20051103074312.GQ11488@ca-server1.us.oracle.com> <20051103165306.GA4923@infradead.org> <20051103205802.31121fc4.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, mark.fasheh@oracle.com, Joel Becker Return-path: Received: from agminet01.oracle.com ([141.146.126.228]:43385 "EHLO agminet01.oracle.com") by vger.kernel.org with ESMTP id S1750801AbVKDSbw (ORCPT ); Fri, 4 Nov 2005 13:31:52 -0500 To: Andrew Morton In-Reply-To: <20051103205802.31121fc4.akpm@osdl.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > So for both -mm and for the ocfs2 team, leaving the patch in the ocfs2 git > tree is the most convenient place for it. Well, I don't think it matters much either way because we mostly test by checking out of svn and buliding against -mm or patched distro kernels. I'd leave the details up to you and Joel (who maintains our ocfs2 git) -- whatever is easiest for you guys. > Obviously, merging it into Linus's tree will fix up everyone's patching > problems, but it has no users at this time... So, speaking of which, are there any barriers to merging OCFS2 now? I think Christoph's concerns (silly /proc files, vma walking, endian stuff) have been addressed. - z