summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2026-08-21 12:08:40 +0200
committerVinod Koul <vkoul@kernel.org>2026-10-03 17:07:38 +0200
commit91967098fd985237ba0deff97809ab52d3e51fba (patch)
tree9f35e0eb62cc2c7f61076be1300bcba7f890b89c /include/linux
parentfdc340bfc7ab60c4cbdb198c9972114b51d7caa3 (diff)
downloadlinux-next-91967098fd985237ba0deff97809ab52d3e51fba.tar.gz
linux-next-91967098fd985237ba0deff97809ab52d3e51fba.zip
phy: rockchip: Make sure clk_init_data is fully initialized
The clk_init_data structure contains several mutually-exclusive members for different methods to specify the possible parents of a clock, prompting drivers to initialize only the members they need. However, not initializing all members may cause subtle issues, which are only exposed when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled. Make sure all members are fully initialized, to avoid such bugs, and to prevent future breakage when converting drivers to a different method for specifying the parents. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Heiko Stuebner <heiko@sntech.de> Reviewed-by: Brian Masney <bmasney@redhat.com> Link: https://patch.msgid.link/adb5bd47343dd31661748d5de14cb28a2bae2d17.1787240165.git.geert+renesas@glider.be Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions