On Mon, 15 May 2017, Benjamin Tissoires wrote:
> On Mon, May 15, 2017 at 10:42 AM, Jani Nikula
> wrote:
>> On Mon, 15 May 2017, Benjamin Tissoires wrote:
>>> I'll answer everything in the other thread, where there are slightly
>>> more other points raised: https://lkml.org/lkml/2017/5/15/10
>>
>
On Mon, May 15, 2017 at 10:42 AM, Jani Nikula
wrote:
> On Mon, 15 May 2017, Benjamin Tissoires wrote:
>> I'll answer everything in the other thread, where there are slightly
>> more other points raised: https://lkml.org/lkml/2017/5/15/10
>
> If you are discussing changes impacting i915, please ke
On Mon, 15 May 2017, Benjamin Tissoires wrote:
> I'll answer everything in the other thread, where there are slightly
> more other points raised: https://lkml.org/lkml/2017/5/15/10
If you are discussing changes impacting i915, please keep intel-gfx list
in the loop.
Thanks,
Jani.
--
Jani Niku
Hi Lv,
On Mon, May 15, 2017 at 5:55 AM, Zheng, Lv wrote:
> Hi, Benjamin
>
>> From: linux-acpi-ow...@vger.kernel.org
>> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Benjamin
>> Tissoires
>> Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open()
>> invocations
>>
>> Hi Lv,
>
Hi, Benjamin
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Benjamin
> Tissoires
> Subject: Re: [PATCH v2 5/5] ACPI: button: Obselete acpi_lid_open() invocations
>
> Hi Lv,
>
> I am trying to reduce the number of parallel discussion we have on
Hi Lv,
I am trying to reduce the number of parallel discussion we have on the
same subject, but there is something here I can't let you have.
On Fri, May 12, 2017 at 8:08 AM, Zheng, Lv wrote:
> Hi,
>
> If my previous reply is not persuasive enough.
> Let me do that in a different way.
>
>> From:
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 returning value. Now listeners needn't invoke acpi_lid_open(),
> it should use a spec suggested control method lid device usage model:
> register lid notificati
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() invocations
>
> Hi,
>
> > Fro
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
On Tue, 09 May 2017, Lv Zheng wrote:
> Since notification side has been changed to always notify kernel listeners
> using _LID returning value. Now listeners needn't invoke acpi_lid_open(),
> it should use a spec suggested control method lid device usage model:
> register lid notification and use
Since notification side has been changed to always notify kernel listeners
using _LID returning value. Now listeners needn't invoke acpi_lid_open(),
it should use a spec suggested control method lid device usage model:
register lid notification and use the notified value instead, which is the
only
11 matches
Mail list logo
