Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: Re: [RFC PATCH v3 5/5] ACPI: button: Always notify kernel space
> using _LID returning value
>
> Hi Lv,
>
> On May 27 2017 or thereabouts, Lv Zheng wrote:
> > Both nouveau and i915, the only 2 kernel space lid noti
questions to PATCH 1-2 discussion and reply in order to stop
this.
We can revisit PATCH 4-5 when the basic questions are answered. :)
>
> On Fri, May 12, 2017 at 8:08 AM, Zheng, Lv wrote:
> > Hi,
> >
> > If my previous reply is not persuasive enough.
> > Let me do t
Hi,
If my previous reply is not persuasive enough.
Let me do that in a different way.
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng,
> Lv
> Subject: RE: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocat
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com]
> Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations
>
> On Tue, May 9, 2017 at 9:02 AM, Lv Zheng wrote:
> > Since notification side has been changed to always notify kernel listeners
> > using _LID
Hi, Ville
Have you reported this to the owner of the backlight core?
This looks like a bug that the backlight core should handle.
What intel backlight driver and acpi backlight driver have done here are just
invoking APIs provided by the backlight core.
So it is the duty of the backlight core to