[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0709191028211.11138@schroedinger.engr.sgi.com>
Date: Wed, 19 Sep 2007 10:29:04 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Anton Altaparmakov <aia21@....ac.uk>
cc: David Rientjes <rientjes@...gle.com>,
Christoph Hellwig <hch@....de>, Mel Gorman <mel@...net.ie>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
David Chinner <dgc@....com>, Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [03/17] is_vmalloc_addr(): Check if an address is within the
vmalloc boundaries
On Wed, 19 Sep 2007, Anton Altaparmakov wrote:
> There even is such a function already in mm/sparse.c::vaddr_in_vmalloc_area()
> with pretty identical content. I would suggest either this new inline should
> go away completely and use the existing one and export it or the existing one
> should go away and the inline should be used. It seems silly to have two
> functions with different names doing exactly the same thing!
Just in case you have not noticed: This patchset removes the
vaddr_in_vmalloc_area() in sparse.c
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists