linux-kernel - Re: [PATCH] dt-bindings: clock: add clock definitions for Ralink SoCs

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: <10e21109-f4fa-42f5-a3fa-c6fa67fba783@kernel.org>
Date: Wed, 15 Jan 2025 09:27:34 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc: linux-clk@...r.kernel.org, sboyd@...nel.org, mturquette@...libre.com,
 robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 yangshiji66@...look.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: add clock definitions for Ralink SoCs

On 14/01/2025 08:43, Sergio Paracuellos wrote:
>>
>>> consumer nodes. So if adding this header is not a possibility with the
>>> changes in the yaml file I will forget about this addition and this
>>> patch.
>>
>> Header without user is pointless. Driver and the DTS are the expected users.
> 
> Understood. So having only DTSs as users is not a possible way to go.
> It is clear now. Forget about this patch then.

Only DTS user, with a justification, would go. Then just resend this
patch when you have at least DTS user.

Best regards,
Krzysztof