Al Viro <[email protected]> wrote:
> Guys, please, look at actual users of that stuff.
I've been and looked at every single user of work_struct in the kernel (at
least, I think I have), and 99% of those just expect data to be the container
of the work_struct or a data structure linked to it. I had to come up with a
way to deal with cases where data is something from which you can't derive
from the work_struct address, but I'm not sure how best to do that for timers.
I haven't, however, been and looked at timers, so I can't say what actually
applies there.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]