Re: [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs()

2008-07-09 Thread Bernhard Walle
Hi, * Simon Horman [2008-07-09 10:41]: On Mon, Jul 07, 2008 at 04:43:41PM +0200, Bernhard Walle wrote: With the previous patch, we have a duplication between that both functions for following tasks: - don't report the interrupt table as RAM, - set the mem_min and mem_max limits for

Re: [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs()

2008-07-08 Thread Simon Horman
On Mon, Jul 07, 2008 at 04:43:41PM +0200, Bernhard Walle wrote: With the previous patch, we have a duplication between that both functions for following tasks: - don't report the interrupt table as RAM, - set the mem_min and mem_max limits for kdump. This patch removes that redundancy

[PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs()

2008-07-07 Thread Bernhard Walle
With the previous patch, we have a duplication between that both functions for following tasks: - don't report the interrupt table as RAM, - set the mem_min and mem_max limits for kdump. This patch removes that redundancy into the function get_memory_ranges() that calls both functions