[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfLMwTEOSKd3cy8j1RuQMwTDFnp_aMzQvod-DJG5e0KVQ@mail.gmail.com>
Date: Tue, 19 Jun 2018 20:04:49 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Daniel Drake <drake@...lessm.com>
Cc: Chris Chiu <chiu@...lessm.com>,
Corentin Chary <corentin.chary@...il.com>,
Darren Hart <dvhart@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
Hans de Goede <hdegoede@...hat.com>,
Linux Upstreaming Team <linux@...lessm.com>
Subject: Re: [PATCH v2 1/2] platform/x86: asus-wmi: Call led hw_changed API on
kbd brightness change
On Tue, Jun 19, 2018 at 7:46 PM, Daniel Drake <drake@...lessm.com> wrote:
>> > Can we avoid those ugly castings?
> Now kbd_led_set can continue being a correctly typed function pointer
> for led_classdev.brightness_set. And from the code you are adding here
> you can call __kbd_led_set directly with signed integer values, and
> rely on correct bounds correction without ugly casts.
>
> Andy, what do you think?
Thanks, Daniel for investigation.
I'm fine with solution(s) that has no ugly casting and no regression
on the hardware we support.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists