From: Benson Leung <bleung@google.com>
To: gregkh@linuxfoundation.org
Cc: enric.balletbo@collabora.com, bleung@chromium.org,
bleung@google.com, bleung@kernel.org, linux-usb@vger.kernel.org,
pmalani@chromium.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Fix for cros_ec_typec for USB for v5.12 merge window
Date: Thu, 4 Feb 2021 11:24:59 -0800 [thread overview]
Message-ID: <YBxKC0IeWBJ/X/wJ@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]
Hi Greg,
I found a bug in the typec driver you pulled earlier this week
and Prashant developed a fix.
The following changes since commit 64eaa0fa66ac55965f793a8b65730299854e55cd:
platform/chrome: cros_ec_typec: Fix call to typec_partner_set_pd_revision (2021-02-02 19:42:52 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-ib-usb-typec-chrome-platform-cros-ec-typec-clear-pd-discovery-events-for-5.12
for you to fetch changes up to c8ec21c6d25c2a8895614ea38575dadb8570c2f9:
platform/chrome: cros_ec_typec: Clear Type C disc events (2021-02-04 10:29:30 -0800)
----------------------------------------------------------------
clear-pd-discovery-events
This pair of patches fixes an issue where cros_ec_typec creates stale
cable nodes on detach because of uncleared pd discovery status events.
----------------------------------------------------------------
Prashant Malani (2):
platform/chrome: cros_ec: Import Type C control command
platform/chrome: cros_ec_typec: Clear Type C disc events
drivers/platform/chrome/cros_ec_typec.c | 29 +++++++++++++++++++++++---
include/linux/platform_data/cros_ec_commands.h | 26 +++++++++++++++++++++++
2 files changed, 52 insertions(+), 3 deletions(-)
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2021-02-04 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 19:24 Benson Leung [this message]
2021-02-05 9:04 ` Greg KH
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=YBxKC0IeWBJ/X/wJ@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=bleung@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.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
all inboxes | Powered by JetHome®