On Tue, Jun 1, 2010 at 11:15 AM, Julia Lawall <julia@xxxxxxx> wrote: > Yes, but the question was more because I was trying to understand whether > the scanner should be looking for ioremap problems or not. Adding Bjorn as he wrote all of the code in the current version of ioremap(). IIRC the original version of ioremap() just did what __ioremap() does now ... people using ioremap() for more creative purposes prompted the complexity to make sure that we didn't mix cacheable and uncacheable accesses. Most core kernel use of ioremap() will still end up in __ioremap() ... so there would be no ill effects from those calls if done from code that holds locks. Are there many spots in arch/ia64 that are flagged? -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|