On Sun, Oct 04, 2015 at 10:46:05AM -0800, Mike Dupuis wrote: > > And I think you just broke the "autoload" logic that these "call a null > > function" function calls were trying to solve, which isn't good at all. > > I guess this bit is lost on me-- how does calling a function from a > previously unused object affect the state of a driver or kernel module? It forces the module where that function is to be loaded into memory before this function can be called. That is if we have multiple modules here, I haven't looked at the code in a long time to verify it, but note, you are totally ignoring the comment put there in the code that says this. greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
