From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Pavel Machek <pavel@kernel.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
bettyzhou@google.com, ynaffit@google.com, tkjos@google.com
Subject: Re: [PATCH v2 0/5] leds: KUnit registration tests pertaining to init_data
Date: Wed, 21 May 2025 23:26:08 +0200 [thread overview]
Message-ID: <e88b295d-eb52-4d42-ae33-232c27f2e1e8@gmail.com> (raw)
In-Reply-To: <20250519133300.GA8794@google.com>
On 5/19/25 15:33, Lee Jones wrote:
> On Sun, 18 May 2025, Jacek Anaszewski wrote:
>
>> Hi Lee,
>>
>> On 5/15/25 10:27, Lee Jones wrote:
>>> Lots of drivers still register with the LED Class using init_data. Let's
>>
>> What do you mean by "still"? Actually init_data is the new approach,
>> that turns the LED core DT parser on, and is predestined for use with
>> {devm_}led_classdev_register_ext() API.
>
> Thanks for the information. I'll update the wording.
Other than that, for the whole series:
Reviewed-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2025-05-21 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:27 Lee Jones
2025-05-15 8:28 ` [PATCH v2 1/5] leds: led-test: Move common LED class registration code into helper function Lee Jones
2025-05-15 8:28 ` [PATCH v2 2/5] leds: led-test: Provide test for registration with missing default_label Lee Jones
2025-05-15 8:28 ` [PATCH v2 3/5] leds: led-test: Provide test for registration with missing devicename Lee Jones
2025-05-15 8:28 ` [PATCH v2 4/5] leds: led-test: Provide test for registration with a name that is too long Lee Jones
2025-05-15 8:28 ` [PATCH v2 5/5] leds: led-test: Provide test for successful registration using init_data Lee Jones
2025-05-18 15:32 ` [PATCH v2 0/5] leds: KUnit registration tests pertaining to init_data Jacek Anaszewski
2025-05-19 13:33 ` Lee Jones
2025-05-21 21:26 ` Jacek Anaszewski [this message]
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=e88b295d-eb52-4d42-ae33-232c27f2e1e8@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=bettyzhou@google.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=tkjos@google.com \
--cc=ynaffit@google.com \
/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
all inboxes | Powered by JetHome®