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.7-rc2
Date: Thu, 16 Apr 2020 14:40:35 -0700 [thread overview]
Message-ID: <20200416214035.GA1586@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
Hi Linus,
The following changes since commit a46387712da12b61bf1ce1a3f63b60a17b098960:
platform/chrome: cros_ec_spi: Wait for USECS, not NSECS (2020-04-07 14:42:08 -0700)
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.7-rc2
for you to fetch changes up to 538b8471fee89eaf18f6bfbbc0576473f952b83e:
platform/chrome: cros_ec_sensorhub: Add missing '\n' in log messages (2020-04-13 16:31:33 +0200)
----------------------------------------------------------------
chrome-platform fixes for v5.7-rc2
Two small fixes for cros_ec_sensorhub_ring.c, addressing issues
introduced in the cros_ec_sensorhub FIFO support commit.
----------------------------------------------------------------
Christophe JAILLET (1):
platform/chrome: cros_ec_sensorhub: Add missing '\n' in log messages
Dan Carpenter (1):
platform/chrome: cros_ec_sensorhub: Off by one in cros_sensorhub_send_sample()
drivers/platform/chrome/cros_ec_sensorhub_ring.c | 8 ++++----
1 file changed, 4 insertions(+), 4 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-04-16 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 21:40 Benson Leung [this message]
2020-04-16 22:15 ` [GIT PULL] chrome-platform fixes for v5.7-rc2 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=20200416214035.GA1586@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).