linux-kernel - Re: [PATCH] dt-bindings: leds: mark label as depected to match description

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: <fdce3c08-a3cb-4d5b-ad1a-0eeb8761778f@collabora.com>
Date: Thu, 9 May 2024 14:39:36 +0200
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 Frank Wunderlich <linux@...web.de>, Pavel Machek <pavel@....cz>,
 Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Conor Dooley <conor+dt@...nel.org>
Cc: Frank Wunderlich <frank-w@...lic-files.de>, linux-leds@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: leds: mark label as depected to match
 description

Il 09/05/24 13:46, Krzysztof Kozlowski ha scritto:
> On 09/05/2024 13:05, Frank Wunderlich wrote:
>> From: Frank Wunderlich <frank-w@...lic-files.de>
>>
>> The description for property 'label' describes it as deprected, so
> 
> Typos here and in subject.
> 
> 
>> add a option to mark it like that. Future devicetrees should use
>> function and color properties.
>>
>> Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
>> Fixes: 24a71afe05a8 ("dt-bindings: leds: Convert common LED binding to schema")
> 
> Nooo, that's not a fix.
> 
> I don't think there was conclusion to make it deprecated on last attempt:
> 
> https://lore.kernel.org/all/20221122111124.6828-1-cniedermaier@dh-electronics.com/
> 

It's not a fix, agreed.

But that property being deprecated deserves to be marked as deprecated, anyway.
Otherwise the documentation shouldn't say in words that it is such.

Cheers,
Angelo