Re: [PATCH ib-mux-pinctrl 1/1] mux: describe np parameter in __devm_mux_state_get()

[Josua Mayer]

Hi Frank,

Am 07.05.26 um 17:21 schrieb Frank Li:
> Add a description for the 'np' parameter of __devm_mux_state_get() to fix
> build warning.
>
> Reported-by: kernel test robot <lkp@xxxxxxxxx>
> Closes: https://lore.kernel.org/oe-kbuild-all/202605061502.ullLjmtN-lkp@xxxxxxxxx/
> Signed-off-by: Frank Li <Frank.Li@xxxxxxx>
> ---
>  drivers/mux/core.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mux/core.c b/drivers/mux/core.c
> index 2f01acfccf47b..5083e3d19606b 100644
> --- a/drivers/mux/core.c
> +++ b/drivers/mux/core.c
> @@ -771,6 +771,7 @@ static void devm_mux_state_release(struct device *dev, void *res)
>   * @dev: The device that needs a mux-state.
>   * @mux_name: The name identifying the mux-state.
>   * @optional: Whether to return NULL and silence errors when mux doesn't exist.
> + * @np: The device nodes, use dev->of_node if it is NULL.
minor nit: Singular device "node".
>   * @init: Optional function pointer for mux-state object initialisation.
>   * @exit: Optional function pointer for mux-state object cleanup on release.
>   *
> --
> 2.43.0
>
Acked-by: Josua Mayer <josua@xxxxxxxxxxxxx>

I think patches to mux-core alone end up in some low-attention (no-)maintainer bin,
when they don't go via other trees (mmc, pinctrl, phy, ...).
See also:

https://lore.kernel.org/r/20260423-mux-smatch-fixup-v1-1-9f403014e0d7@xxxxxxxxxxxxx