Re: [PATCH 0/5] Clocklib: generic clocks framework

[Pavel Machek]

Hi!

> > WTF? There are currently around 10 copies of clock code in the tree,
> > every one slightly different. If this can help us get rid of all that
> > crap, that's a GOOD THING, normative or not.
> 
> At the expense of people going off and inventing their own APIs because
> they find that the "normatived" clock API doesn't do what they need to?

Just now, everyone just cuts&copies clock.c. I do not think "new"
situation can worse than that.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/