On 3/4/26 6:57 PM, Vladimir Oltean wrote: > Some pragmatic shortcuts are being taken by PHY consumer driver authors, > which put a burden on the framework. A lot of these can be caught during > review. > > Make sure the linux-phy list is copied on as many keywords that a regex > can reasonably catch. > > For simplicity sake this is not perfect (devm_ and of_ are not valid > prefixes for all function names), but I tried to pay attention on > avoiding false matches on things like: > - drivers/net/vendor/device/phy.h > - include/linux/phy.h - network PHY, not generic PHY > > So I used \b to try to match on actual word boundaries and be explicit > about what is matched on. > > Signed-off-by: Vladimir Oltean <[email protected]> > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 55af015174a5..bdfa47d9c774 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -10713,6 +10713,7 @@ F: Documentation/devicetree/bindings/phy/ > F: drivers/phy/ > F: include/dt-bindings/phy/ > F: include/linux/phy/ > +K: > \b(devm_)?(of_)?phy_(create|destroy|init|exit|reset|power_(on|off)|configure|validate|calibrate|(get|set)_(mode|media|speed|bus_width|drvdata)|get_max_link_rate|pm_runtime_(get|put)|notify_(connect|disconnect|state)|get|put|optional_get|provider_(un)?register|simple_xlate|(create|remove)_lookup)\b|(struct\s+)?phy(_ops|_attrs|_lookup|_provider)?\b|linux/phy/phy\.h|phy-props\.h|phy-provider\.h
Would looking for the devm/of_phy_ prefix followed by an open parentheses not suffice for the 'has function call' case, instead of listing all currently present exported functions? My worry is that this approach is overbuilt and absolutely no one will remember to update it Konrad
