From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 3 Mar 2008 11:04:24 -0800 (PST) From: Christoph Lameter Subject: Re: [PATCH] mmu notifiers #v8 In-Reply-To: <20080303033428.GD3301@wotan.suse.de> Message-ID: References: <20080219084357.GA22249@wotan.suse.de> <20080219135851.GI7128@v2.random> <20080219231157.GC18912@wotan.suse.de> <20080220010941.GR7128@v2.random> <20080220103942.GU7128@v2.random> <20080221045430.GC15215@wotan.suse.de> <20080221144023.GC9427@v2.random> <20080221161028.GA14220@sgi.com> <20080227192610.GF28483@v2.random> <20080302155457.GK8091@v2.random> <20080303033428.GD3301@wotan.suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: Andrea Arcangeli , Jack Steiner , akpm@linux-foundation.org, Robin Holt , Avi Kivity , Izik Eidus , kvm-devel@lists.sourceforge.net, Peter Zijlstra , general@lists.openfabrics.org, Steve Wise , Roland Dreier , Kanoj Sarcar , linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com List-ID: On Mon, 3 Mar 2008, Nick Piggin wrote: > Move definition of struct mmu_notifier and struct mmu_notifier_ops under > CONFIG_MMU_NOTIFIER to ensure they doesn't get dereferenced when they > don't make sense. The callbacks take a mmu_notifier parameter. So how does this compile for !MMU_NOTIFIER? -- 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