[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <65eda66d-a6cd-408f-ad00-c23b8f675a73@web.de>
Date: Mon, 3 Nov 2025 09:05:25 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc: Michael Turquette <mturquette@...libre.com>, Nishanth Menon <nm@...com>,
Raag Jadav <raag.jadav@...el.com>, Santosh Shilimkar <ssantosh@...nel.org>,
Stephen Boyd <sboyd@...nel.org>, Tero Kristo <kristo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>,
Jonathan Corbet <corbet@....net>
Subject: Re: clk: keystone: sci-clk: use devm_kmemdup_array() once more in
ti_sci_scan_clocks_from_fw()
>>>> Fixes: 3c13933c60338ce6fb2369bd0e93f91e52ddc17d ("clk: keystone: sci-clk: add support for dynamically probing clocks")
Will further adjustments become more helpful for the affected function implementation?
Regards,
Markus
Powered by blists - more mailing lists