On Wed, 13 Jun 2018, Baolin Wang wrote: > We have introduced the persistent clock framework to support the OS time > compensating from persistent clock, and we will convert all drivers to > use common persistent clock framework instead of the persistent clock > support used only for the ARM architecture. So we can remove these code > with converting the Omap 32k counter and tegra20 timer. Why did I look at that in the first place? But as I did, I just have to say, it's just consistent trainwreck engineering. Remove working code first and then add new one. Hell NO! This is not how it works. We add new infrastructure - if required with some extra temporary helpers - while keeping the existing functionality intact. Then we convert the users of the old infrastructure over and when the last user is gone, we remove that including all temporary helpers. That's not something fundamentally new. It's documented all over the place. Thanks, tglx -- 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
