From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AB15BC5DF94 for ; Mon, 24 Aug 2026 21:44:41 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [127.0.0.1]) by lists.ozlabs.org (Postfix) with ESMTP id 4hTPZb5n27z2y2c; Tue, 25 Aug 2026 07:44:39 +1000 (AEST) Authentication-Results: lists.ozlabs.org; arc=none smtp.remote-ip=185.11.138.130 ARC-Seal: i=1; a=rsa-sha256; d=lists.ozlabs.org; s=201707; t=1787607879; cv=none; b=g2J0kl1PDzbzyJ0nNZI2aXP+wOymCam1W/P2AtQdQNcmOGUrprN/WT0O8KCLzNk+skTDLyw28njbhgJLgeG4db+qxjmuzgaQu5mZDZww5iySlhnYwb/XyzU3QYKk4qHfhOlaCp8gpL8mSCc9UIPplO7f6mAHsN1zXAAFjS/L5eMrZFLQTm8EdQLkhaln1xSgfbT4anYHargaI8qRcG7QIy4Z8BogFQb9g5p+XrEDrod8w+Q9RwwbEROr9uTD9h1KonDGuMjmUy/B18fTeG0MCp0pE5oEFgEP1D8bEZ9hTh3bEvugIwS2j4N4iiu4BAXyzTmeRy4SW/0tvFmRQiQZYg== ARC-Message-Signature: i=1; a=rsa-sha256; d=lists.ozlabs.org; s=201707; t=1787607879; c=relaxed/relaxed; bh=jVWHXt5kccAnCww2YkWc7+CJixLQqoOYi0ZBcColNt0=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=M8fTlUejAXXpJn3t7sBpsy55nWvd22E5LX3yZlirzDcSgtnYakP5Eduu1M/FGaui3WAecHkppBoXpgMFHwtQHmkaiWGyofHkGILYMIRXSheM07jnCTQKrVYjCfKj5LK8q1oks4+mshUkP12vJts4plx9ILGwC1065+dg/SIeQg05MNRDlT7nXnTHyni63D6fj/yJOZDPgjAJx5wnTlt9ryUKRm8F1YRbwMEcQk1bH0oNKk/YvCk3sWfaDnuIqytPvGoi77Z5vp7Mr2Z7D6ajrDzD/OUJvTTT1lNMrCoFM4Ve5UC1L+60cNUPJr2ut/QCI841vNpwFG34YAs/KgQpsA== ARC-Authentication-Results: i=1; lists.ozlabs.org; dmarc=pass (p=quarantine dis=none) header.from=sntech.de; dkim=pass (2048-bit key; secure) header.d=sntech.de header.i=@sntech.de header.a=rsa-sha256 header.s=gloria202408 header.b=gWJzN7dM; dkim-atps=neutral; spf=pass (client-ip=185.11.138.130; helo=gloria.sntech.de; envelope-from=heiko@sntech.de; receiver=lists.ozlabs.org) smtp.mailfrom=sntech.de Authentication-Results: lists.ozlabs.org; dmarc=pass (p=quarantine dis=none) header.from=sntech.de Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; secure) header.d=sntech.de header.i=@sntech.de header.a=rsa-sha256 header.s=gloria202408 header.b=gWJzN7dM; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=sntech.de (client-ip=185.11.138.130; helo=gloria.sntech.de; envelope-from=heiko@sntech.de; receiver=lists.ozlabs.org) X-Greylist: delayed 1924 seconds by postgrey-1.37 at boromir; Tue, 25 Aug 2026 07:44:33 AEST Received: from gloria.sntech.de (gloria.sntech.de [185.11.138.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4hTPZT2gNCz2xZh; Tue, 25 Aug 2026 07:44:29 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sntech.de; s=gloria202408; h=Content-Type:Content-Transfer-Encoding:MIME-Version: References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Reply-To; bh=jVWHXt5kccAnCww2YkWc7+CJixLQqoOYi0ZBcColNt0=; b=gWJzN7dM/JTTPxhl+cIzoI7bqh xTglornZsWzyUT6gAWwHlVLJetXnZ2Z5EMuCLuAg11XlHgvf1Wk6a0btrtLN5HhjjAG2Q7UH6bgeO 5pNpJ0MEntul+ICrSfwFAc4fEk57NsAyll35Dcvwjx0oFXGnLlTCERbbZn+mD4nieMTql+KosEbZ5 inUdcsXbrlIQoUmUoxvJUnR4iJIkSUSNyx7MXP5QpUmuaGKDqp5W4m9eiveS9GyjB0lnwBJYC7Lm9 QtCoKLycKYO2D/67maCOOnaxcZahjOMGWSvtkjJmVar4K8lyd1CaB5mAfEoncOElmin1FKJV0R227 TIkdKuAg==; From: Heiko =?UTF-8?B?U3TDvGJuZXI=?= To: Ryan Chen , Joel Stanley , Stephen Boyd , Brian Masney , Jerome Brunet , Andrew Jeffery , Billy Tsai , Nicolas Ferre , Alexandre Belloni , Claudiu Beznea , Ray Jui , Scott Branden , Broadcom internal kernel review list , Taichi Sugaya , Takao Orito , Linus Walleij , Avi Fishman , Tomer Maimon , Tali Perry , Patrick Venture , Nancy Yuen , Benjamin Fair , Sudeep Holla , Cristian Marussi , David Lechner , Abel Vesa , Peng Fan , Frank Li , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Paul Cercueil , Santosh Shilimkar , Andrew Lunn , Gregory Clement , Sebastian Hesselbarth , Vladimir Zapolskiy , Krzysztof Kozlowski , Sylwester Nawrocki , Chanwoo Choi , Peter Griffin , Alim Akhtar , Dinh Nguyen , Viresh Kumar , Maxime Coquelin , Alexandre Torgue , Emilio =?UTF-8?B?TMOzcGV6?= , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Prashant Gaikwad , Thierry Reding , Jonathan Hunter , Kunihiko Hayashi , Masami Hiramatsu , Ulf Hansson , Liviu Dudau , Lorenzo Pieralisi , Michal Simek , Matthias Brugger , Geert Uytterhoeven 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, Geert Uytterhoeven Subject: Re: [PATCH 00/45] clk: Make sure clk_init_data is fully initialized (part two) Date: Mon, 24 Aug 2026 23:11:32 +0200 Message-ID: <3074509.irdbgypaU6@diego> In-Reply-To: References: X-Mailing-List: linux-aspeed@lists.ozlabs.org List-Id: List-Help: List-Owner: List-Post: List-Archive: , List-Subscribe: , , List-Unsubscribe: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Hi Geert, Am Freitag, 21. August 2026, 10:53:10 Mitteleurop=C3=A4ische Sommerzeit sch= rieb Geert Uytterhoeven: > Hi all, >=20 > 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. >=20 > Hence this series aims to 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. >=20 > Part One[1] fixed all cases that I identified to be real bugs, in > response to a crash I saw on BeagleBone Black. >=20 > This series is the clock subpart of Part Two, which fixes remaining > cases that are currently harmless. These are still fragile, and may > cause future breakage when converting drivers to a different method for > specifying the parents. >=20 > Thanks for your comments! I guess more a handling question, how do you expect this series to be applied? I.e. each clk-arch-maintainer, or in one big thing by the core clock maintainers? Just wondering if I should pick the Rockchip patch or just let the whole series get applied by the clock maintainers. Heiko