On Thu, Apr 16, 2015 at 01:29:19PM -0400, Garret Kelly wrote: > fbtft uses fb_info's screen_base field to store a non-__iomem > allocation. Cast away the __iomem qualifier when freeing the pointer to > suppress the sparse warning.
Can't we fix this properly, to use the correct type of pointer instead for non-__iomem allocations? thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
