summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/parse_data_structs.py
diff options
context:
space:
mode:
authorJohan Hovold <johan@kernel.org>2026-06-04 14:59:12 +0300
committerMark Brown <broonie@kernel.org>2026-06-04 18:59:39 +0300
commite727fe9be1738ebc0caa5cc901f0299404b6bbe6 (patch)
treebce4b8ae197211a53f9a9ea56a8c7cdfae337121 /tools/lib/python/kdoc/parse_data_structs.py
parentd6621c9beecb72ed7598b718741c8c11539e3bd4 (diff)
downloadlinux-e727fe9be1738ebc0caa5cc901f0299404b6bbe6.tar.xz
regulator: bq257xx: drop confusing configuration of_node
The driver reuses the OF node of the parent multi-function device but still sets the of_node field of the regulator configuration to any prior OF node. Since the MFD child device does not have an OF node set until probe is called, this field is set to NULL on first probe and to the reused OF node if the driver is later rebound. As the device_set_of_node_from_dev() helper drops a reference to any prior OF node before taking a reference to the new one this can apparently also confuse LLMs like Sashiko which flags it as a potential use-after-free (which it is not). Drop the confusing and redundant configuration of_node assignment. Link: https://sashiko.dev/#/patchset/20260408073055.5183-1-johan%40kernel.org Signed-off-by: Johan Hovold <johan@kernel.org> Link: https://patch.msgid.link/20260604115912.2734074-1-johan@kernel.org Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/parse_data_structs.py')
0 files changed, 0 insertions, 0 deletions