From: Benson Leung <bleung@google.com>
To: bleung@chromium.org, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, jekarlson@gmail.com,
narmstrong@baylibre.com, enric.balletbo@collabora.com,
olof@lixom.net
Subject: [GIT PULL] chrome-platform fixes for v4.19-rc8
Date: Tue, 9 Oct 2018 21:23:18 -0700 [thread overview]
Message-ID: <20181010042318.GA142005@decatoncale.mtv.corp.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hi Greg,
Sorry for the late in the cycle request, but this one is fairly urgent.
Please pull thi fix to chrome platform. A patch that landed
for 4.19 broke cros_ec based chromebooks' keyboards, and this fixes them.
Thanks,
Benson
The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21:
Linux 4.19-rc7 (2018-10-07 17:26:02 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/tag-chrome-platform-fixes-for-v4.19-rc8
for you to fetch changes up to d4d2313a3c17eff4aef9a544023c2df5b9f5bedc:
mfd: cros-ec: copy the whole event in get_next_event_xfer (2018-10-09 20:57:30 -0700)
----------------------------------------------------------------
chrome-platform-fixes-for-v4.19-rc8
This contains a fix to 57e94c8b974db2d83c60e1139c89a70806abbea0, which caused
cros_ec based chromebooks to truncate an entire column of their built-in
keyboard.
----------------------------------------------------------------
Emil Karlson (1):
mfd: cros-ec: copy the whole event in get_next_event_xfer
drivers/platform/chrome/cros_ec_proto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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: 833 bytes --]
next reply other threads:[~2018-10-10 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 4:23 Benson Leung [this message]
2018-10-10 9:14 ` 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=20181010042318.GA142005@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=jekarlson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=olof@lixom.net \
/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
Powered by JetHome