All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: bleung@chromium.org, chrome-platform@lists.linux.dev,
	tzungbi@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] chrome-platform updates for v7.2
Date: Mon, 15 Jun 2026 03:16:07 +0000	[thread overview]
Message-ID: <ai9ud-vLUe2pj9M2@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3184 bytes --]

Hi Linus,

Please pull chrome-platform updates for Linux v7.2.

Thanks,
Tzung-Bi
------

The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:

  Linux 7.1-rc3 (2026-05-10 14:08:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-v7.2

for you to fetch changes up to 883f968dcbb08a155101e3a943557530d4ac0463:

  platform/chrome: Prevent build for big-endian systems (2026-06-02 03:14:10 +0000)

----------------------------------------------------------------
chrome-platform: Updates for v7.2

* Improvements

  - Use named initializers for struct i2c_device_id.

* Fixes

  - Fix a probe race between cros_ec_sensorhub and cros_ec_sysfs.
  - Check for the presence of ACPI_COMPANION() for drivers converted
    from acpi_driver to platform_driver to avoid issues where
    device_match_driver_override() might forcibly match the driver to
    the device.
  - Fix a possible UAF in cros_ec_chardev.
  - Prevent build for big-endian systems as CHROME_PLATFORMS drivers are
    only running and testing under little-endian systems.

* Cleanups

  - Drop some redundant bits in cros_kbd_led_backlight and Kconfig.

----------------------------------------------------------------
Rafael J. Wysocki (3):
      platform/chrome: chromeos_privacy_screen: Check ACPI_COMPANION()
      platform/chrome: chromeos_tbmc: Check ACPI_COMPANION()
      platform/chrome: wilco_ec: event: Check ACPI_COMPANION()

Thomas Weißschuh (5):
      platform/chrome: cros_kbd_led_backlight: Drop max_brightness from driver data
      platform/chrome: cros_kbd_led_backlight: Pass keyboard_led as parameter
      platform/chrome: cros_kbd_led_backlight: Drop CONFIG_MFD_CROS_EC_DEV ifdeffery
      platform/chrome: Remove superfluous dependencies from CROS_EC
      platform/chrome: Prevent build for big-endian systems

Tzung-Bi Shih (5):
      platform/chrome: Resolve kb_wake_angle visibility race
      platform/chrome: cros_ec_chardev: Introduce chardev_data
      platform/chrome: cros_ec_chardev: Move data to chardev_pdata
      platform/chrome: cros_ec_chardev: Add event relayer
      platform/chrome: cros_ec_chardev: Introduce rwsem for protecting ec_dev

Uwe Kleine-König (The Capable Hub) (1):
      platform/chrome: Use named initializers for struct i2c_device_id

 drivers/platform/chrome/Kconfig                   |   2 +-
 drivers/platform/chrome/chromeos_privacy_screen.c |   3 +
 drivers/platform/chrome/chromeos_tbmc.c           |   6 +-
 drivers/platform/chrome/cros_ec_chardev.c         | 146 +++++++++++++++++-----
 drivers/platform/chrome/cros_ec_i2c.c             |   2 +-
 drivers/platform/chrome/cros_ec_sensorhub.c       |   6 +-
 drivers/platform/chrome/cros_ec_sysfs.c           |   5 +-
 drivers/platform/chrome/cros_hps_i2c.c            |   2 +-
 drivers/platform/chrome/cros_kbd_led_backlight.c  |  28 ++---
 drivers/platform/chrome/wilco_ec/event.c          |   8 +-
 include/linux/platform_data/cros_ec_proto.h       |   2 +
 11 files changed, 150 insertions(+), 60 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-06-15  3:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15  3:16 Tzung-Bi Shih [this message]
2026-06-16  2:11 ` [GIT PULL] chrome-platform updates for v7.2 pr-tracker-bot

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=ai9ud-vLUe2pj9M2@google.com \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.