There this boot-time message (on both omap3 and am3517 evms atleast): [ 1.904418] omap_device: omap_wdt.-1: new worst case activate latency 0: 6105 omap_init_wdt() initializes the id to -1 and then omap_device_build() is called with this value; this eventually calls platform_device_register() with a pdev having id as -1. I don't see any code that checks for this -1 and changes it to a non-erroneous value. Perhaps there is a reason I've failed to notice? Please comment. Else I'm planning to submit a patch which fixes this. - Abhilash -- 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
