From: patchwork-bot+chrome-platform@kernel.org
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: rafael@kernel.org, lenb@kernel.org, hdegoede@redhat.com,
markgross@kernel.org, bleung@chromium.org, eballetbo@gmail.com,
gregkh@linuxfoundation.org, kernel@collabora.com,
groeck@chromium.org, dtor@chromium.org, gwendal@chromium.org,
vbendeb@chromium.org, andy@infradead.org,
ayman.bagabas@gmail.com, benjamin.tissoires@redhat.com,
blaz@mxxn.io, dvhart@infradead.org, dmitry.torokhov@gmail.com,
jeremy@system76.com, 2pi@mok.nu, mchehab+samsung@kernel.org,
rajatja@google.com, srinivas.pandruvada@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
rafael.j.wysocki@intel.com, chrome-platform@lists.linux.dev
Subject: Re: [PATCH v13] platform/chrome: Add ChromeOS ACPI device driver
Date: Mon, 16 May 2022 01:50:12 +0000 [thread overview]
Message-ID: <165266581207.6997.10229505003935532310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Yn4OKYrtV35Dv+nd@debian-BULLSEYE-live-builder-AMD64>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 13 May 2022 12:52:09 +0500 you wrote:
> From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>
> The x86 Chromebooks have the ChromeOS ACPI device. This driver attaches
> to the ChromeOS ACPI device and exports the values reported by ACPI in a
> sysfs directory. This data isn't present in ACPI tables when read
> through ACPI tools, hence a driver is needed to do it. The driver gets
> data from firmware using the ACPI component of the kernel. The ACPI values
> are presented in 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 device's sysfs directory tree. This data is
> consumed by the ChromeOS user space.
>
> [...]
Here is the summary with links:
- [v13] platform/chrome: Add ChromeOS ACPI device driver
https://git.kernel.org/chrome-platform/c/0a4cad9c11ad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-16 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:52 [PATCH v13] platform/chrome: Add ChromeOS ACPI device driver Muhammad Usama Anjum
2022-05-13 11:50 ` patchwork-bot+chrome-platform
2022-05-16 1:50 ` patchwork-bot+chrome-platform [this message]
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=165266581207.6997.10229505003935532310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=blaz@mxxn.io \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=dvhart@infradead.org \
--cc=eballetbo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=hdegoede@redhat.com \
--cc=jeremy@system76.com \
--cc=kernel@collabora.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rajatja@google.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=usama.anjum@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox