From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org
Cc: bleung@kernel.org, bleung@chromium.org, bleung@google.com,
enric.balletbo@collabora.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] chrome-platform fixes for v5.5-rc7
Date: Thu, 16 Jan 2020 09:58:02 -0800 [thread overview]
Message-ID: <20200116175802.GA147875@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hi Linus,
The following changes since commit 856a0a6e2d09d31fd8f00cc1fc6645196a509d56:
platform/chrome: wilco_ec: fix use after free issue (2019-12-02 12:14:42 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-fixes-for-v5.5-rc7
for you to fetch changes up to dfb9a8857f4decbba8c2206e8877e1d741ee1b47:
platform/chrome: wilco_ec: Fix keyboard backlight probing (2020-01-10 14:57:58 -0800)
----------------------------------------------------------------
platform/chrome fixes for v5.5-rc7.
One fix in the wilco_ec keyboard backlight driver
to allow the EC driver to continue loading in the absence
of a backlight module.
----------------------------------------------------------------
Daniel Campello (1):
platform/chrome: wilco_ec: Fix keyboard backlight probing
drivers/platform/chrome/wilco_ec/keyboard_leds.c | 28 +++++++++++++++++-------
1 file changed, 20 insertions(+), 8 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:[~2020-01-16 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 17:58 Benson Leung [this message]
2020-01-16 18:30 ` [GIT PULL] chrome-platform fixes for v5.5-rc7 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=20200116175802.GA147875@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=bleung@kernel.org \
--cc=enric.balletbo@collabora.com \
--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.