[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfGRNo4hvKV7caQE6i2rHVncOjxDv3-b9oGrpK-uDEBRw@mail.gmail.com>
Date: Thu, 14 Mar 2024 12:34:54 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: George Stark <gnstark@...utedevices.com>
Cc: pavel@....cz, lee@...nel.org, vadimp@...dia.com, mpe@...erman.id.au,
npiggin@...il.com, christophe.leroy@...roup.eu, hdegoede@...hat.com,
mazziesaccount@...il.com, peterz@...radead.org, mingo@...hat.com,
will@...nel.org, longman@...hat.com, boqun.feng@...il.com,
nikitos.tr@...il.com, marek.behun@....cz, kabel@...nel.org,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, kernel@...utedevices.com
Subject: Re: [PATCH v6 9/9] leds: powernv: use LED_RETAIN_AT_SHUTDOWN flag for leds
On Thu, Mar 14, 2024 at 10:46 AM George Stark <gnstark@...utedevices.com> wrote:
>
> This driver wants to keep its LEDs state after module is removed
> and implemented it in its own way. LED subsystem supports dedicated
> flag LED_RETAIN_AT_SHUTDOWN for the same purpose so use the flag
> instead of custom implementation.
So, this change is not related to the main purpose of the series...
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists