On Sun, Nov 24, 2013 at 09:36:11AM -0300, Ezequiel Garcia wrote: > In order to remove the following ugly message: > > BUG: mapping for 0x00000000 at 0xff000000 out of vmalloc space > > the iotable mappings should be re-located inside the vmalloc > region. Such move was introduced at commit: > > commit 0536bdf33faff4d940ac094c77998cfac368cfff > Author: Nicolas Pitre <[email protected]> > Date: Thu Aug 25 00:35:59 2011 -0400 > > ARM: move iotable mappings within the vmalloc region > > While at it, let's add some nicer defines to make the code > more readable. > > Cc: Nicolas Pitre <[email protected]> > Signed-off-by: Ezequiel Garcia <[email protected]>
NAK. I'm guessing that you haven't properly tested this. Grep for UNCACHED_PHYS_0, and what you'll find is that your change will break standby and suspend on all PXA platforms. -- 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/
