All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Benson Leung <bleung@chromium.org>,
	chrome-platform@lists.linux.dev
Subject: Re: [PATCH v1 0/3] platform/chrome: Check ACPI_COMPANION() against NULL at probe time
Date: Wed, 13 May 2026 02:22:16 +0000	[thread overview]
Message-ID: <agPgWFhTfLoJSSeX@google.com> (raw)
In-Reply-To: <3710526.iIbC2pHGDl@rafael.j.wysocki>

On Tue, May 12, 2026 at 06:34:06PM +0200, Rafael J. Wysocki wrote:
> Hi All,
> 
> This series fixes up three platform/chrome drivers recently converted to
> platform drivers to make them check the devices' ACPI companion objects at
> probe time.
> 
> Thanks!
> 

Applied to

    https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next

[1/3] platform/chrome: chromeos_privacy_screen: Check ACPI_COMPANION()
      commit: 8a4a217f617b1ac2f8c095f33efd67d947ddb2cf
[2/3] platform/chrome: chromeos_tbmc: Check ACPI_COMPANION()
      commit: c15dbae7c856fb53cc6ffb86c6c64ebb816d07c8
[3/3] platform/chrome: wilco_ec: event: Check ACPI_COMPANION()
      commit: 51dcff9796fd486d7abf01081ca62e4072789e9d

Thanks!

      parent reply	other threads:[~2026-05-13  2:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 16:34 [PATCH v1 0/3] platform/chrome: Check ACPI_COMPANION() against NULL at probe time Rafael J. Wysocki
2026-05-12 16:35 ` [PATCH v1 1/3] platform/chrome: chromeos_privacy_screen: Check ACPI_COMPANION() Rafael J. Wysocki
2026-05-12 16:35 ` [PATCH v1 2/3] platform/chrome: chromeos_tbmc: " Rafael J. Wysocki
2026-05-12 16:36 ` [PATCH v1 3/3] platform/chrome: wilco_ec: event: " Rafael J. Wysocki
2026-05-13  2:22 ` Tzung-Bi Shih [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=agPgWFhTfLoJSSeX@google.com \
    --to=tzungbi@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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.