lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 26 Sep 2018 20:48:54 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Jian-Hong Pan <jian-hong@...lessm.com>
Cc:     Corentin Chary <corentin.chary@...il.com>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Upstreaming Team <linux@...lessm.com>
Subject: Re: [RFC PATCH] platform/x86: asus-wmi: Simplify the keyboard
 brightness updating process

On Mon, Sep 10, 2018 at 11:57 AM Jian-Hong Pan <jian-hong@...lessm.com> wrote:
>
> 2018-08-16 16:41 GMT+08:00 Jian-Hong Pan <jian-hong@...lessm.com>:
> > The original asus-wmi queues a work which calls the ACPI/WMI methods to
> > update the keyboard LED brightness.  Similar drivers - acer-wmi,
> > dell-wmi-led just call the ACPI/WMI methods directly without workqueues.
> >
> > This patch simplifies the keyboard brightness updating process which
> > calls the kbd_led_update function directly without workqueue in
> > asus-wmi.

> Just gentle ping.  Any comment for this patch?

RFC patches are not supposed to be applied.
So, feel free to resend as non-RFC, or wait a bit more if anyone would
comment on it.

-- 
With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ