On Sun, Mar 08, 2026 at 11:40:44AM -0700, Joe Perches wrote: > On Sun, 2026-03-08 at 13:40 +0200, [email protected] wrote: > > diff --git a/MAINTAINERS b/MAINTAINERS > [] > > @@ -10713,6 +10713,17 @@ F: Documentation/devicetree/bindings/phy/ > > +K: (?:linux/phy/phy\.h|phy-props\.h|phy-provider\.h) > > phy-props.h and phy-provider.h don't seem to exist. > Are these going to be added later?
They're actually provided by patch 13/24: https://lore.kernel.org/linux-phy/[email protected]/T/#u ./include/linux/phy/phy-props.h ./drivers/phy/phy-provider.h > Maybe this should be phy-common-props.h ? No, that's unrelated. > Perhaps if matching only the include uses: > (/ is escaped because get_maintainer is stupid) > something like: > > K: include\s*\<linux\/phy\/phy(?:-common-props|-provider)?\.h\> Why is get_maintainer stupid? I ran git format-patch -1 0fc83bd79589b (random patch which includes <linux/phy/phy.h> and I got: GENERIC PHY FRAMEWORK status: Supported:Keyword:(?:linux/phy/phy\.h|phy-props\.h|phy-provider\.h) GENERIC PHY FRAMEWORK status: Supported:Keyword:\b(?:devm_)?(?:of_)?phy_(?:optional_)?(?:get|put)(?:_by_index)?\b GENERIC PHY FRAMEWORK status: Supported:Keyword:\bphy_(?:init|exit|power_(?:on|off))\b GENERIC PHY FRAMEWORK status: Supported:Keyword:\bphy_(?:get|set)_(?:mode(?:_ext)?|media|speed|bus_width|max_link_rate)\b GENERIC PHY FRAMEWORK status: Supported:Keyword:\bstruct\s+phy(?:_ops|_attrs|_lookup|_provider)?\b which seems to be OK, it matched the (?:linux/phy/phy\.h|phy-props\.h|phy-provider\.h) regex.
