linux-kernel - Re: [PATCH v13] platform/chrome: Add ChromeOS ACPI device driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165266581207.6997.10229505003935532310.git-patchwork-notify@kernel.org>
Date:   Mon, 16 May 2022 01:50:12 +0000
From:   patchwork-bot+chrome-platform@...nel.org
To:     Muhammad Usama Anjum <usama.anjum@...labora.com>
Cc:     rafael@...nel.org, lenb@...nel.org, hdegoede@...hat.com,
        markgross@...nel.org, bleung@...omium.org, eballetbo@...il.com,
        gregkh@...uxfoundation.org, kernel@...labora.com,
        groeck@...omium.org, dtor@...omium.org, gwendal@...omium.org,
        vbendeb@...omium.org, andy@...radead.org, ayman.bagabas@...il.com,
        benjamin.tissoires@...hat.com, blaz@...n.io, dvhart@...radead.org,
        dmitry.torokhov@...il.com, jeremy@...tem76.com, 2pi@....nu,
        mchehab+samsung@...nel.org, rajatja@...gle.com,
        srinivas.pandruvada@...ux.intel.com,
        platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-acpi@...r.kernel.org, rafael.j.wysocki@...el.com,
        chrome-platform@...ts.linux.dev
Subject: Re: [PATCH v13] platform/chrome: Add ChromeOS ACPI device driver

Hello:

This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@...nel.org>:

On Fri, 13 May 2022 12:52:09 +0500 you wrote:
> From: Enric Balletbo i Serra <enric.balletbo@...labora.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