> > IMHO you should be free to bump the module reference count up and down
> > as you wish, and be able to read the module reference count.
> > If you make that assumption, then it becomes possible to use the module
> > ref count as an internal reference counter, for device opens or
> > something like that.
> Surely the exception rather than the rule?
> Sorry, complicating the code and making everyone pay the penalty so
> you can take a confusing short cut in your code is not something we're
> going to agree on.
Actually, having uniform interface between kernel and modules is very
nice... And one int per module does not surely hurt, does it?
Perhaps #define NEED_USE_COUNT to do it on per-module basis?
-- I'm firstname.lastname@example.org. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at email@example.com - 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/