m Driver
> <platform-driver-...@vger.kernel.org>; quasi...@google.com; Pali Rohár
> <pali.ro...@gmail.com>
> Subject: Re: [PATCH 09/12] platform/x86: wmi: create character devices when
> requested by drivers
>
> On Thu, Sep 21, 2017 at 4:57 PM, Mario Limonciello
> <mario.li
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Thursday, September 21, 2017 11:47 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; LKML ; Platform Driver
> ; quasi...@google.com; Pali Rohár
>
> Subject: Re: [PATCH
On Thu, Sep 21, 2017 at 4:57 PM, Mario Limonciello
wrote:
> For WMI operations that are only Set or Query read or write sysfs
> attributes created by WMI vendor drivers make sense.
>
> For other WMI operations that are run on Method, there needs to be a
> way to
On Thu, Sep 21, 2017 at 4:57 PM, Mario Limonciello
wrote:
> For WMI operations that are only Set or Query read or write sysfs
> attributes created by WMI vendor drivers make sense.
>
> For other WMI operations that are run on Method, there needs to be a
> way to guarantee to userspace that the
For WMI operations that are only Set or Query read or write sysfs
attributes created by WMI vendor drivers make sense.
For other WMI operations that are run on Method, there needs to be a
way to guarantee to userspace that the results from the method call
belong to the data request to the method
For WMI operations that are only Set or Query read or write sysfs
attributes created by WMI vendor drivers make sense.
For other WMI operations that are run on Method, there needs to be a
way to guarantee to userspace that the results from the method call
belong to the data request to the method
6 matches
Mail list logo