From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lameter Subject: Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries Date: Wed, 19 Sep 2007 10:29:40 -0700 (PDT) Message-ID: References: <20070919033605.785839297@sgi.com> <20070919033641.009931707@sgi.com> <167F960F-0A93-4263-8AE6-1B0CEBB2C9D1@cam.ac.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: David Rientjes , Christoph Hellwig , Mel Gorman , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, David Chinner , Jens Axboe To: Anton Altaparmakov Return-path: Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:35234 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751181AbXISR3l (ORCPT ); Wed, 19 Sep 2007 13:29:41 -0400 In-Reply-To: <167F960F-0A93-4263-8AE6-1B0CEBB2C9D1@cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > I suspect that is_vmalloc_addr() should not be in linux/mm.h at all and should > be in linux/vmalloc.h instead and vmalloc.h should include linux/highmem.h. > That would be more sensible than sticking a vmalloc related function into > linux/mm.h where it does not belong... Tried it and that leads to all sort of other failures.