On Monday 16 September 2002 13:52, Adrian Bunk wrote:
> This change results in a compile error in the ATM drivers:
Yep, There are even many other places where xtime is used which may result in
the same kind of compilation problems. Two possible solutions come to mind:
* Maintain both the ordinary xtime (timeval) and an xtime_nsec (timespec).
xtime may then be a timeval shadow value of xtime_nsec.
* Just fix it everywhere.
I cannot tell fore sure which option Linus prefers, but I think ...
Some places may even have other problems as well (e.g. ATM drivers): xtime is
a complex data type which needs read_lock / read_unlock, but there's no
locking in many places.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:17 EST