On 26-03-05 21:15:32, Krzysztof Wilczyński wrote:
> 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.
For content match, it could also be:
K: phy
I believe this would match everything of interest? Perhaps there is no
need to have any of these complex regular expressions, would be my way of
thinking here. Makes it easier to maintain, too.
Just thinking out loud, really...
Krzysztof
