Re: [PATCH] ASoC: rockchip: fix device node reference leak in rk3288_hdmi_analog

[Krzysztof Kozlowski <krzk@kernel.org>]

On Fri, 09 Oct 2026 02:14:59 +0800, Haotian Zhang wrote:
> snd_rk_mc_probe() acquires references to the codec and CPU device nodes
> with of_parse_phandle() and stores them in the static rk_dailink, but the
> driver never calls of_node_put() on them. All error paths and the success
> path simply return, and the driver has no remove callback, so the
> references are leaked for the whole lifetime of the card and each failed
> or repeated probe leaks another pair. The same pattern was fixed for the
> sibling rockchip_rt5645.c driver.
> 
> Release the codec and CPU device nodes on every probe error path and in a
> new remove callback, and also drop the extra reference placed in args.np
> by of_parse_phandle_with_fixed_args().
> 
> Fixes: eaae2ea73593 ("ASoC: rockchip: Add machine driver for RK3288 boards that use analog/HDMI")
> Assisted-by: DeepSeek-V4.1-Flash
> Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
> ---
>  sound/soc/rockchip/rk3288_hdmi_analog.c | 42 +++++++++++++++++++------
>  1 file changed, 33 insertions(+), 9 deletions(-)
> 



Multiple things here:
1. Your team ignored completely previous feedback.

2. You use multiple identities with this email, thus I actually doubt we speak
   with actual person.

3. Finally, same feedback:
You sent multiple independent patches, to multiple independent
subsystems. The amount of these patches clearly suggest this was
AI generated and most likely not tested.

More importantly, you sent all this work without properly organizing
relevant patches into patchsets. This makes reviewing difficult
and might cause multiple reviewers to address the same issue.
Replying to the entire set is impossible and requires handling each
patch independently, instead of applying or discarding the set.
Maintainers also won't see the bigger picture of your work. Quite
worrying.

This is on the verge of hostile patch: bomb us with so many
contributions, we won't be able to handle them in efficient manner,
like responding ONCE to ask you to slow down.  Considering all this
is untested and LLM generated, I have even more doubts whether this
should be considered for review.

Please read kernel documentation BEFORE posting more work. It will
explain you how to identify subsystems, how to organize your work per
subsystem (so a patchset grouping multiple patches with a short cover
letter), how to document usage of LLM and how what you should not do
if this was posted in a good faith.

Best regards,
Krzysztof