linux-kernel - Re: [PATCH v5 27/31] clk: at91: at91rm9200: switch to parent_hw and parent

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <daddf1b7-ef48-4dcb-8c69-301b883b5729@tuxon.dev>
Date: Sat, 31 Jan 2026 16:13:24 +0200
From: Claudiu Beznea <claudiu.beznea@...on.dev>
To: ryan.wanner@...rochip.com, mturquette@...libre.com, sboyd@...nel.org,
 nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
 bmasney@...hat.com, alexander.sverdlin@...il.com,
 varshini.rajendran@...rochip.com
Cc: cristian.birsan@...rochip.com, balamanikandan.gunasundar@...rochip.com,
 linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 27/31] clk: at91: at91rm9200: switch to parent_hw and
 parent_data

The driver is using now only parent_data. This is valid for all the SoC specific 
driver patches in this series, no? So, better drop the parent_hw from the title 
and description. Valid for all the patches in the series with this symptom. E.g. 
have it like "clk: at91: at91rm9200: switch to parent_data"

On 1/16/26 22:07, ryan.wanner@...rochip.com wrote:
> From: Claudiu Beznea<claudiu.beznea@...on.dev>
> 
> Switch AT91RM9200 clocks to use parent_hw and parent_data where possible.
> Having parent_hw instead of parent names improves to clock registration
> speed and re-parenting. Update clock registration functions to use
> clk_hw struct.

Same here as in case of patch 24/31.

Also, for all the soc specific patches

> 
> Signed-off-by: Claudiu Beznea<claudiu.beznea@...on.dev>
> Signed-off-by: Ryan Wanner<Ryan.Wanner@...rochip.com>

With all the above addressed:

Reviewed-by: Claudiu Beznea <claudiu.beznea@...on.dev>