[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c5a8768-2d19-40b9-a965-966a8900e703@gmail.com>
Date: Sun, 18 May 2025 17:32:42 +0200
From: Jacek Anaszewski <jacek.anaszewski@...il.com>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: bettyzhou@...gle.com, ynaffit@...gle.com, tkjos@...gle.com
Subject: Re: [PATCH v2 0/5] leds: KUnit registration tests pertaining to
init_data
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.
> provide some additional Kunit infrastructure to exercise the various
> possibilities.
>
> Change log:
>
> v1 => v2:
> - Use devm_* to ensure resources are cleaned-up on exit
>
> Lee Jones (5):
> leds: led-test: Move common LED class registration code into helper
> function
> leds: led-test: Provide test for registration with missing
> default_label
> leds: led-test: Provide test for registration with missing devicename
> leds: led-test: Provide test for registration with a name that is too
> long
> leds: led-test: Provide test for successful registration using
> init_data
>
> drivers/leds/led-test.c | 86 ++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 80 insertions(+), 6 deletions(-)
>
--
Best regards,
Jacek Anaszewski
Powered by blists - more mailing lists