* Toshi Kani <toshi.kani@xxxxxxx> wrote: > On x86, ioremap() and remap_pfn_range() already fail on a conflicting cache > type if it is not allowed by the rule defined in is_new_memtype_allowed(). > This exception handling is necessary for remap_pfn_range() called by > /dev/mem, but I do not think it's necessary for ioremap(). I think we can > start from adding a warning message to ioremap(). Agreed, we should warn and map the situation before doing any behavioral change that isn't a fix. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
