I'd suggest "It fails in order to [...]" to avoid the "does work
exactly NOT as advertised" ambiguity ;-)
> Q: But modules call my register() routine which wants to call back
> into one of the function pointers immediately, and so
> try_module_get() fails!
> A: You're being called from the module, so someone already has a
> reference (unless there's a bug), so you don't need a
Hmm, I haven't really looked at your new code, but this sounds as
if try_module_get gets an exclusive lock. Is this true ? Doesn't
seem to make sense to me.
> Hope that helps?
Don't you want to repeat the golden rule at the end, just as a
polite reminder ? :-) (Just kidding.)
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina email@example.com / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/