[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ea54a95-213e-41cb-1bf8-bc72475d1f73@collabora.com>
Date: Mon, 30 Mar 2020 17:38:23 +0200
From: Enric Balletbo i Serra <enric.balletbo@...labora.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, groeck@...omium.org,
bleung@...omium.org, dtor@...omium.org, gwendal@...omium.org,
Collabora Kernel ML <kernel@...labora.com>,
vbendeb@...omium.org, andy@...radead.org,
Ayman Bagabas <ayman.bagabas@...il.com>,
Darren Hart <dvhart@...radead.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Jeremy Soller <jeremy@...tem76.com>,
Jonathan Corbet <corbet@....net>,
Krzysztof Kozlowski <krzk@...nel.org>,
Mattias Jacobsson <2pi@....nu>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Rajat Jain <rajatja@...gle.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Yauhen Kharuzhy <jekhor@...il.com>,
platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH v3] platform: x86: Add ACPI driver for ChromeOS
Hi Greg,
On 30/3/20 17:34, Greg Kroah-Hartman wrote:
> On Mon, Mar 30, 2020 at 05:06:17PM +0200, Enric Balletbo i Serra wrote:
>> This driver attaches to the ChromeOS ACPI device and then exports the values
>> reported by the ACPI in a sysfs directory. These values are not exported
>> via the standard ACPI tables, hence a specific driver is needed to do
>> it. The ACPI values are presented in the string form (numbers as decimal
>> values) or binary blobs, and can be accessed as the contents of the
>> appropriate read only files in the standard ACPI devices sysfs directory tree.
>
> Any reason why you didn't send this to the ACPI maintainers and
> developer mailing list?
>
Right, one should never only trust on what get_maintainers returns you. My bad,
I'll cc them. Thanks for pointing it.
Thanks,
Enric
> They would be the best ones to review this...
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists