> +@ defines_module_init exists @ > +declarer name module_init; > +identifier init; > +@@ > + > +module_init(init); > + > +@ has_probe depends on defines_module_init @ > +identifier drv_calls, drv_probe; > +type bus_driver; > +identifier probe_op =~ "(probe)"; > +@@ > + > +bus_driver drv_calls = { > + .probe_op = drv_probe, > +};
I'm not sure that this is enough. For example, there is the macro platform_driver_probe that initializes probe fields. There is likewise module_platform_driver, which is a top-level declaration that encapsulates the module_init and the definition of the module_init function, which in turn calls platform_driver_probe. There is also module_platform_driver, which encapsulates the module_init, but not the initialization of the probe field. Are you concerned with any of these cases? julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/