From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, groeck@chromium.org,
bleung@chromium.org, dtor@chromium.org, gwendal@chromium.org,
Collabora Kernel ML <kernel@collabora.com>,
vbendeb@chromium.org, andy@infradead.org,
Ayman Bagabas <ayman.bagabas@gmail.com>,
Darren Hart <dvhart@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jeremy Soller <jeremy@system76.com>,
Jonathan Corbet <corbet@lwn.net>,
Krzysztof Kozlowski <krzk@kernel.org>,
Mattias Jacobsson <2pi@mok.nu>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Rajat Jain <rajatja@google.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Yauhen Kharuzhy <jekhor@gmail.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3] platform: x86: Add ACPI driver for ChromeOS
Date: Mon, 30 Mar 2020 17:34:30 +0200 [thread overview]
Message-ID: <20200330153430.GA750889@kroah.com> (raw)
In-Reply-To: <20200330150617.1132570-1-enric.balletbo@collabora.com>
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?
They would be the best ones to review this...
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-30 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 15:06 [PATCH v3] platform: x86: Add ACPI driver for ChromeOS Enric Balletbo i Serra
2020-03-30 15:34 ` Greg Kroah-Hartman [this message]
2020-03-30 15:38 ` Enric Balletbo i Serra
2020-03-30 17:29 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200330153430.GA750889@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=bleung@chromium.org \
--cc=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=dvhart@infradead.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jekhor@gmail.com \
--cc=jeremy@system76.com \
--cc=kernel@collabora.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajatja@google.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vbendeb@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.