lkml.org 
[lkml]   [2015]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] firmware: annotate thou shalt not request fw on init or probe
> +@ 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


\
 
 \ /
  Last update: 2015-08-29 18:41    [W:0.156 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site