Hello,
> > > K:
> > > \b(?:__)?(?:devm_)?(?:of_)?phy_(?:create|destroy|provider_(?:un)?register)\b
> > > K: \bphy_(?:create|remove)_lookup\b
> > > K: \bphy_(?:get|set)?_drvdata\b
> > > K: \b(?:devm_)?(?:of_)?phy_(?:optional_)?(?:get|put)(?:_by_index)?\b
> > > K: \bphy_pm_runtime_(?:get|put)(?:_sync)?\b
> > > K: \bphy_(?:init|exit|power_(?:on|off))\b
> > > K:
> > > \bphy_|(?:get|set)_(?:mode(?:_ext)?|media|speed|bus_width|max_link_rate)\b
> > > K: \bphy_(?:reset|configure|validate|calibrate)\b
> > > K: \bphy_notify_(?:connect|disconnect|state)\b
> > > K: (?:struct\s+)?phy(?:_ops|_attrs|_lookup|_provider)?\b
> > > K: (?:linux/phy/phy\.h|phy-props\.h|phy-provider\.h)
> >
> > What about
> >
> > F: drivers/*/*phy*
> >
> > or something along these lines.
> >
> > Krzysztof
>
> I don't understand your suggestion. Is it meant as a replacement for the
> keyword regexes? Your file pattern matches on:
I was thinking more along the lines of using wildcards, the F: was just an
example.
[...]
> There are a lot of false positives, and a lot of false negatives.
Yeah, the "catch-all", for lack of better word, will not work here.
Krzysztof
