From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: pmalani@chromium.org, bleung@chromium.org, groeck@chromium.org,
tzungbi@kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev
Subject: [GIT PULL] chrome-platform changes for v6.13
Date: Mon, 18 Nov 2024 00:32:10 +0000 [thread overview]
Message-ID: <ZzqLCvx94JhkBmEP@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-for-6.13
for you to fetch changes up to ea45f3f46734a47bdbcfb31f41748484219d2ea6:
platform/chrome: Switch back to struct platform_driver::remove() (2024-10-28 08:48:34 +0000)
----------------------------------------------------------------
chrome platform changes for 6.13
* Fixes
- Fix a leak of fwnode refcount.
* Cleanups
- Drop unused I2C driver data.
- Move back from platform_driver::remove_new() to
platform_driver::remove().
----------------------------------------------------------------
Javier Carrasco (1):
platform/chrome: cros_ec_typec: fix missing fwnode reference decrement
Uwe Kleine-König (2):
platform/chrome: Drop explicit initialization of struct i2c_device_id::driver_data to 0
platform/chrome: Switch back to struct platform_driver::remove()
drivers/platform/chrome/cros_ec_chardev.c | 2 +-
drivers/platform/chrome/cros_ec_debugfs.c | 2 +-
drivers/platform/chrome/cros_ec_i2c.c | 2 +-
drivers/platform/chrome/cros_ec_lightbar.c | 2 +-
drivers/platform/chrome/cros_ec_lpc.c | 2 +-
drivers/platform/chrome/cros_ec_sysfs.c | 2 +-
drivers/platform/chrome/cros_ec_typec.c | 3 ++-
drivers/platform/chrome/cros_ec_vbc.c | 2 +-
drivers/platform/chrome/cros_hps_i2c.c | 2 +-
drivers/platform/chrome/cros_typec_switch.c | 2 +-
drivers/platform/chrome/cros_usbpd_logger.c | 2 +-
drivers/platform/chrome/cros_usbpd_notify.c | 4 ++--
drivers/platform/chrome/wilco_ec/core.c | 2 +-
drivers/platform/chrome/wilco_ec/debugfs.c | 2 +-
drivers/platform/chrome/wilco_ec/telemetry.c | 2 +-
15 files changed, 17 insertions(+), 16 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-11-18 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 0:32 Tzung-Bi Shih [this message]
2024-11-19 19:06 ` [GIT PULL] chrome-platform changes for v6.13 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=ZzqLCvx94JhkBmEP@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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