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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: Anton Altaparmakov <[email protected]>
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- References:
- [00/17] [RFC] Virtual Compound Page Support
- From: Christoph Lameter <[email protected]>
- [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: Christoph Lameter <[email protected]>
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: David Rientjes <[email protected]>
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: Anton Altaparmakov <[email protected]>
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: David Rientjes <[email protected]>
- Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- From: Anton Altaparmakov <[email protected]>
- [00/17] [RFC] Virtual Compound Page Support
- Prev by Date: Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- Next by Date: Re: Intel Memory Ordering White Paper
- Previous by thread: Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- Next by thread: Re: [03/17] is_vmalloc_addr(): Check if an address is within the vmalloc boundaries
- Index(es):