public inbox for chrome-platform@lists.linux.dev
 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 v6.19
Date: Mon, 1 Dec 2025 03:52:15 +0000	[thread overview]
Message-ID: <aS0Q71JuMYM56FZ0@google.com> (raw)

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

Hi Linus,

Please pull chrome-platform updates for Linux v6.19.

Thanks,
Tzung-Bi
------

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-v6.19

for you to fetch changes up to 52075d2c7595cfd6c1ce211a9cd138a9b067c448:

  platform/chrome: sensorhub: Support devices without FIFO_INT_ENABLE (2025-11-14 02:57:32 +0000)

----------------------------------------------------------------
chrome-platform: Updates for v6.19

* Improvements

  - Support legacy probe behavior in cros_ec_lightbar and
    cros_ec_sensorhub.

* Fixes

  - Don't fall back to legacy probe behavior if it isn't a legacy device
    in cros_usbpd_notify.
  - Fix an UAF after unbinding driver in cros_ec_ishtp.

----------------------------------------------------------------
Brady Norander (1):
      platform/chrome: cros_ec_lightbar: Check if ec supports suspend commands

Diogo Ivo (1):
      platform/chrome: sensorhub: Support devices without FIFO_INT_ENABLE

Jameson Thies (1):
      platform/chrome: cros_usbpd_notify: defer probe when parent EC driver isn't ready

Tzung-Bi Shih (1):
      platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver

 drivers/platform/chrome/cros_ec_ishtp.c          |  1 +
 drivers/platform/chrome/cros_ec_lightbar.c       | 16 ++++++++++++----
 drivers/platform/chrome/cros_ec_sensorhub_ring.c | 11 +++++++++++
 drivers/platform/chrome/cros_usbpd_notify.c      | 17 +++++++++++++++--
 4 files changed, 39 insertions(+), 6 deletions(-)

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

             reply	other threads:[~2025-12-01  3:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  3:52 Tzung-Bi Shih [this message]
2025-12-04 19:27 ` [GIT PULL] chrome-platform updates for v6.19 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=aS0Q71JuMYM56FZ0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox