From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with ESMTP id 931336B0055 for ; Mon, 20 Jul 2009 05:59:31 -0400 (EDT) Subject: Re: [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() From: Benjamin Herrenschmidt In-Reply-To: <20090720080502.GG7298@wotan.suse.de> References: <20090715074952.A36C7DDDB2@ozlabs.org> <20090715135620.GD7298@wotan.suse.de> <1248073873.13067.31.camel@pasglop> <20090720080502.GG7298@wotan.suse.de> Content-Type: text/plain Date: Mon, 20 Jul 2009 19:59:21 +1000 Message-Id: <1248083961.30899.5.camel@pasglop> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Nick Piggin Cc: Linux Memory Management , Linux-Arch , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Hugh Dickins , Linus Torvalds List-ID: On Mon, 2009-07-20 at 10:05 +0200, Nick Piggin wrote: > > Unless anybody has other preferences, just send it straight to Linus in > the next merge window -- if any conflicts did come up anyway they would > be trivial. You could just check against linux-next before doing so, and > should see if it is going to cause problems for any arch pull... Well, the problem is that powerpc-next will need that patch, which means that if I don't put it in my tree, Steven won't be able to build powerpc-next as part of linux-next until the patch is merged. Hence my question, what's the best way to handle that :-) There isn't an mm-next is there ? If there was, I could tell Steven to always pull powerpc after mm for example. Or I can put it in a git tree of its own with a dependency for Steven to pull. Cheers, Ben. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org