Re: [PATCH 3/3] mm: Change __remove_pages() to call release_mem_region_adjustable()

2013-04-02 Thread Yasuaki Ishimatsu
Hi Toshi, 2013/04/03 1:17, Toshi Kani wrote: > Changed __remove_pages() to call release_mem_region_adjustable(). > This allows a requested memory range to be released from > the iomem_resource table even if it does not match exactly to > an resource entry but still fits into. The resource

[PATCH 3/3] mm: Change __remove_pages() to call release_mem_region_adjustable()

2013-04-02 Thread Toshi Kani
Changed __remove_pages() to call release_mem_region_adjustable(). This allows a requested memory range to be released from the iomem_resource table even if it does not match exactly to an resource entry but still fits into. The resource entries initialized at bootup usually cover the whole

[PATCH 3/3] mm: Change __remove_pages() to call release_mem_region_adjustable()

2013-04-02 Thread Toshi Kani
Changed __remove_pages() to call release_mem_region_adjustable(). This allows a requested memory range to be released from the iomem_resource table even if it does not match exactly to an resource entry but still fits into. The resource entries initialized at bootup usually cover the whole

Re: [PATCH 3/3] mm: Change __remove_pages() to call release_mem_region_adjustable()

2013-04-02 Thread Yasuaki Ishimatsu
Hi Toshi, 2013/04/03 1:17, Toshi Kani wrote: Changed __remove_pages() to call release_mem_region_adjustable(). This allows a requested memory range to be released from the iomem_resource table even if it does not match exactly to an resource entry but still fits into. The resource entries