On Wed, 04 Nov 2026 02:53:43 +0000, Wentao Liang wrote:
> it6505_parse_dt() obtains an endpoint node with
> of_graph_get_endpoint_by_regs() and drops that reference with
> of_node_put() right away, before the node is checked and passed to
> it6505_get_data_lanes_count(), of_property_read_u32_array() and
> of_property_read_variable_u64_array().
>
> The reference from of_graph_get_endpoint_by_regs() is the only thing
> keeping the endpoint alive, so releasing it first leaves the following
> property lookups operating on a node that another of_node_put() can free
> concurrently, for instance when a device tree overlay providing the
> endpoint is removed.
>
> Keep the reference until the properties have been read and only then
> call of_node_put(), for both endpoints parsed by the function.
>
> Fixes: 380d920b582d ("drm/bridge: add it6505 driver to read data-lanes and
> link-frequencies from dt")
> Cc: [email protected]
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <[email protected]>
> ---
> drivers/gpu/drm/bridge/ite-it6505.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Multiple things here:
1. Your team ignored completely previous feedback. Multiple times.
2. You use multiple identities with this email address, thus I doubt that we
speak with an actual person.
3. Your bot does not even bother running checkpatch, right?
4. Nothing of this was reproduced nor tested.
5. Finally, the 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 the issue discovery method and what was
or was not tested.
Best regards,
Krzysztof