> #ifndef CLOCK_TICK_RATE > #define CLOCK_TICK_RATE 1193182 > #endif > > to include/linux/timex.h. Since al existing architectures already define > CLOCK_TICK_RATE as a macro, I don't see anything changing for them. > > The only difference would be that all architectures that use the default > value can have an empty timex.h. > > Am I missing something? Currently if you create a new architecture you have to figure out what your equivalent tick rate is or you get an error for not defining it. Ditto if you try to build code using it on platforms that it is meaningless (eg S/390) you get an error. You'd lose that rather useful property. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
