devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Pavel Machek <pavel@ucw.cz>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Rob Herring <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	kernel <kernel@dh-electronics.com>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: leds: Mark label property as deprecated
Date: Thu, 22 Dec 2022 15:01:44 +0100	[thread overview]
Message-ID: <3c555cae-999f-ccd2-d114-00b92abd19ba@denx.de> (raw)
In-Reply-To: <Y6RgjV4FT57SaTQw@duo.ucw.cz>

On 12/22/22 14:50, Pavel Machek wrote:
> Hi!
> 
>>>> This part I understand. What is not clear to me is, why is 'label' being
>>>> un-deprecated.
>>>
>>> It shouldn't be. It seems to be Pavel's ad-hoc decision.
>>
>> Is there a majority agreement that the "label" property remains
>> deprecated?
> 
> 
>> If so, I would say we can mark the label as deprecated.
>>
>> On the other hand, the new generated standardized sysfs name does not seem
>> to provide a full replacement for the "label" property.
>> What is still missing?
> 
> Having reasonable naming of the LEDs is pre-requisite for deprecating
> label property.

As far as I can tell, function and function-enumerator is the reasonable 
naming. Jacek seem to confirm that. I would say, label can be deprecated 
. What is the counter-argument for why it should NOT be deprecated ?

  reply	other threads:[~2022-12-22 14:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 11:11 [PATCH] dt-bindings: leds: Mark label property as deprecated Christoph Niedermaier
2022-11-22 11:11 ` [PATCH] dt-bindings: mfd: da9062: Correct file name for watchdog Christoph Niedermaier
2022-11-29 12:33   ` Krzysztof Kozlowski
2022-11-30 10:10     ` Lee Jones
2022-11-30 10:13       ` kernel
2022-11-30 10:19       ` Krzysztof Kozlowski
2022-11-30 10:20         ` Lee Jones
2022-11-30 10:18     ` Christoph Niedermaier
2022-11-22 11:11 ` [PATCH] dt-bindings: mmc: Make comment on wakeup-source less confusing Christoph Niedermaier
2022-11-29 12:06   ` Ulf Hansson
2022-11-29 12:33     ` Krzysztof Kozlowski
2022-11-29 12:35   ` Krzysztof Kozlowski
2022-11-29 15:30     ` Ulf Hansson
2022-11-29 15:37       ` Marek Vasut
2022-11-29 15:59       ` Krzysztof Kozlowski
2022-11-22 12:23 ` [PATCH] dt-bindings: leds: Mark label property as deprecated Pavel Machek
2022-11-25 21:26   ` Marek Vasut
2022-11-29  9:03     ` Christoph Niedermaier
2022-11-30 19:19     ` Rob Herring
2022-11-30 19:26       ` Pavel Machek
2022-12-01 21:47         ` Rob Herring
2022-12-02  9:25           ` Pavel Machek
2022-12-01 23:44         ` Marek Vasut
2022-12-01 23:41       ` Marek Vasut
2022-12-05 18:44         ` Jacek Anaszewski
2022-12-22  9:36           ` Christoph Niedermaier
2022-12-22 13:50             ` Pavel Machek
2022-12-22 14:01               ` Marek Vasut [this message]
2022-12-22 14:56                 ` Pavel Machek
2022-12-22 15:21                   ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3c555cae-999f-ccd2-d114-00b92abd19ba@denx.de \
    --to=marex@denx.de \
    --cc=cniedermaier@dh-electronics.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=kernel@dh-electronics.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).