On Fri, 12 Aug 2011, Bjarne Steinsbo wrote: > The warning from omap_display has not been fixed. I could do > something similar to what hsmmc.c is using, but I think this is > unnessarily complex. I think the real fix for this warning is to make > the type of the returned value from > omap_pm_get_dev_context_loss_count() be the same as the prototype in > struct omap_dss_board_info. I can't see why one should be u32, and > the other int. However, I don't know which to fix.. This one should be fixed in the 3.2 time frame by this patch: "[PATCHv2 01/28] OMAP: change get_context_loss_count ret value to int" http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg50692.html - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
