"Adam J. Richter" <adam@yggdrasil.com> writes:
> The is a small change to struct timer in pre7-4. Instead of
> each timer having "prev" and "next" links, management of the doubly
> linked list is handled with a struct "list", which contains the
> "next" and "prev" fields. I am assuming that the semanitics of
> things like list.next == NULL are the same as the old next == NULL
> semantics, and so on. On that assumption, here is a patch that adjusts
> the rest of the kernel to the change that appeared in parts of pre7-4,
> so that the whole kernel compiles, at least on x86 (we build with
> every driver turned on, almost all as modules).
Driver which are manually setting the prev & next member of their
timer structure are wrong <grin>.
There is a macros called init_timer() (linux/timer.h) which is
specifically designed for that.
When the list change, only the macros need to be changed.
--
-- Yoann, http://www.mandrakesoft.com/~yoann/
It is well known that M$ products don't call free() after a malloc().
The Unix community wish them good luck for their future developments.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:15 EST