From: David Lechner <david@lechnology.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>, Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
arm-scmi@vger.kernel.org, imx@lists.linux.dev,
linux-mips@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, soc@lists.linux.dev,
linux-stm32@st-md-mailman.stormreply.com,
linux-sunxi@lists.linux.dev, linux-tegra@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 08/45] clk: davinci: Make sure clk_init_data is fully initialized
Date: Fri, 21 Aug 2026 08:45:04 -0500 [thread overview]
Message-ID: <1f791d6c-48c4-4266-87d0-c70438ec793d@lechnology.com> (raw)
In-Reply-To: <f3b503ff3fda049988c3e16071bbbfabf1b04629.1787239813.git.geert+renesas@glider.be>
On 8/21/26 3:53 AM, Geert Uytterhoeven wrote:
> 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>
> ---
(had to trim the recipients to get my mail server to let me send the message)
Reviewed-by: David Lechner <david@lechnology.com>
next prev parent reply other threads:[~2026-08-21 13:45 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 8:53 [PATCH 00/45] clk: Make sure clk_init_data is fully initialized (part two) Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 01/45] clk: aspeed: Make sure clk_init_data is fully initialized Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 02/45] clk: at91: " Geert Uytterhoeven
2026-08-21 13:39 ` Nicolas Ferre
2026-08-21 8:53 ` [PATCH 03/45] clk: bcm: iproc: " Geert Uytterhoeven
2026-08-24 20:42 ` Florian Fainelli
2026-08-21 8:53 ` [PATCH 04/45] clk: berlin: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 05/45] clk: cdce925: " Geert Uytterhoeven
2026-08-21 11:25 ` Liviu Dudau
2026-08-21 8:53 ` [PATCH 06/45] clk: clk-axi-clkgen: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 07/45] clk: cs2000-cp: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 08/45] clk: davinci: " Geert Uytterhoeven
2026-08-21 13:45 ` David Lechner [this message]
2026-08-21 8:53 ` [PATCH 09/45] clk: fractional-divider: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 10/45] clk: gemini: " Geert Uytterhoeven
2026-08-24 20:39 ` Linus Walleij
2026-08-21 8:53 ` [PATCH 11/45] clk: highbank: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 12/45] clk: hisilicon: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 13/45] clk: imx: " Geert Uytterhoeven
2026-08-21 11:44 ` Abel Vesa
2026-08-21 8:53 ` [PATCH 14/45] clk: ingenic: " Geert Uytterhoeven
2026-08-21 10:57 ` Paul Cercueil
2026-08-21 8:53 ` [PATCH 15/45] clk: keystone: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 16/45] clk: lmk04832: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 17/45] clk: mediatek: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 18/45] clk: milbeaut: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 19/45] clk: mmp: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 20/45] clk: mvebu: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 21/45] clk: mxs: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 22/45] clk: nomadik: " Geert Uytterhoeven
2026-08-24 20:39 ` Linus Walleij
2026-08-21 8:53 ` [PATCH 23/45] clk: npcm7xx: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 24/45] clk: nxp: " Geert Uytterhoeven
2026-08-21 11:52 ` Vladimir Zapolskiy
2026-08-21 8:53 ` [PATCH 25/45] clk: pistachio: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 26/45] clk: pwm: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 27/45] clk: renesas: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 28/45] clk: rockchip: " Geert Uytterhoeven
2026-08-21 14:04 ` Sebastian Reichel
2026-08-24 21:10 ` Heiko Stübner
2026-08-21 8:53 ` [PATCH 29/45] clk: samsung: " Geert Uytterhoeven
2026-08-21 11:04 ` Krzysztof Kozlowski
2026-08-24 12:41 ` Geert Uytterhoeven
2026-08-24 13:16 ` Brian Masney
2026-08-21 8:53 ` [PATCH 30/45] clk: scpi: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 31/45] clk: silabs: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 32/45] clk: socfpga: " Geert Uytterhoeven
2026-08-21 13:31 ` Dinh Nguyen
2026-08-21 8:53 ` [PATCH 33/45] clk: spear: " Geert Uytterhoeven
2026-08-24 4:06 ` Viresh Kumar
2026-08-21 8:53 ` [PATCH 34/45] clk: stm32: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 35/45] clk: st: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 36/45] clk: sunxi: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 37/45] clk: tegra: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 38/45] clk: uniphier: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 39/45] clk: ux500: " Geert Uytterhoeven
2026-08-23 20:30 ` Linus Walleij
2026-08-25 8:00 ` Ulf Hansson
2026-08-21 8:53 ` [PATCH 40/45] clk: versatile: " Geert Uytterhoeven
2026-08-21 11:28 ` Liviu Dudau
2026-08-24 20:43 ` Linus Walleij
2026-08-21 8:53 ` [PATCH 41/45] clk: vt8500: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 42/45] clk: x86: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 43/45] clk: xgene: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 44/45] clk: xilinx: " Geert Uytterhoeven
2026-08-21 8:53 ` [PATCH 45/45] clk: zynqmp: " Geert Uytterhoeven
2026-08-24 15:14 ` [PATCH 00/45] clk: Make sure clk_init_data is fully initialized (part two) Brian Masney
2026-08-24 21:11 ` Heiko Stübner
2026-08-25 15:11 ` Brian Masney
2026-08-25 15:28 ` Heiko Stübner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f791d6c-48c4-4266-87d0-c70438ec793d@lechnology.com \
--to=david@lechnology.com \
--cc=arm-scmi@vger.kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=geert+renesas@glider.be \
--cc=imx@lists.linux.dev \
--cc=jbrunet+clk@baylibre.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=ryan_chen@aspeedtech.com \
--cc=sboyd@kernel.org \
--cc=soc@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox