> struct likeliness {
> char *file;
> int line;
> atomic_t true_count;
> atomic_t false_count;
> struct likeliness *next;
> };
It seems including atomic.h inside compiler.h is a bit tricky (might have interdependency).
Can we just live with int instead of atomic_t? We don't really care about losing a count occasionally..
> It'll crash if a module gets registered then unloaded.
> CONFIG_MODULE_UNLOAD=n would be required.
What about init data that is thrown away after boot?
Hua
-
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/
[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]
