linux-kernel - Re: [PATCH] clk: ti: Simplify ti_find_clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175054082614.4372.10566518984855625833@lazor>
Date: Sat, 21 Jun 2025 14:20:26 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Michael Turquette <mturquette@...libre.com>, Rob Herring (Arm) <robh@...nel.org>, Tero Kristo <kristo@...nel.org>
Cc: linux-omap@...r.kernel.org, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clk: ti: Simplify ti_find_clock_provider()

Quoting Rob Herring (Arm) (2025-03-12 09:33:30)
> Remove using for_each_of_allnodes_from() which is not safe to use
> without holding the DT spinlock. In reality that probably doesn't
> matter here. This is the only user in the whole tree, so it can be
> made private once removed here. The "from" argument is always NULL, so
> it can be dropped as well.
> 
> There's a slight change in behavior in matching the "clock-output-names"
> value as the prior code would match if the node name matched the
> beginning of the value and the comparision was case insensitive. Now
> it must be an exact match.
> 
> Signed-off-by: Rob Herring (Arm) <robh@...nel.org>
> ---

Applied to clk-next