[PATCH v3 5/5] doc: phy: Document some bulk helper functions

[sashiko-bot at kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] docs: phy: linking to unmerged patches in official documentation
--

commit 409a8664a48e7380c1575514d92de3906af9ad4f
Author: Inochi Amaoto <inochiama at gmail.com>

doc: phy: Document some bulk helper functions

Document all newly added bulk helper function, it can be used to manage
a set of PHYs automatically. This is useful when the driver want to
simplify the management of multiple PHYs.

> diff --git a/Documentation/driver-api/phy/phy.rst b/Documentation/driver-api/phy/phy.rst
> index 0865c2e94eece..c5d3d7cc1a74b 100644
> --- a/Documentation/driver-api/phy/phy.rst
> +++ b/Documentation/driver-api/phy/phy.rst

[ ... ]

> @@ -221,3 +245,8 @@ DeviceTree Binding
>  
>  The documentation for PHY dt binding can be found @
>  Documentation/devicetree/bindings/phy/phy-bindings.txt
> +
> +Missing Bulk Helpers
> +====================
> +Currently, Only a few bulk helper functions are added as they have users.
> +Function not upstreamed can be found at https://lore.kernel.org/linux-phy/20260904083709.425893-1-inochiama@gmail.com/

[Severity: Low]
Is it appropriate to include links to out-of-tree, unmerged patches in the
official kernel API documentation?

Should this reference be moved to the commit message or cover letter instead,
and only added to the documentation once the additional helpers are upstreamed
alongside their users?

Additionally, there are minor grammatical issues in this section ("Currently,
Only a few", "Function not upstreamed").

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260923023304.78428-1-inochiama@gmail.com?part=5