All of lore.kernel.org
 help / color / mirror / Atom feed
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-rc5
Date: Wed, 6 May 2020 15:47:37 -0700	[thread overview]
Message-ID: <20200506224737.GA159981@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

Hi Linus,

The following changes since commit 538b8471fee89eaf18f6bfbbc0576473f952b83e:

  platform/chrome: cros_ec_sensorhub: Add missing '\n' in log messages (2020-04-13 16:31:33 +0200)

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-rc5

for you to fetch changes up to b31d1d2b1c3a8452f425b09ebd374ecd3ddd5179:

  platform/chrome: cros_ec_sensorhub: Allocate sensorhub resource before claiming sensors (2020-04-29 23:17:45 +0200)

----------------------------------------------------------------
chrome-platform  fixes for v5.7-rc5

Fix a resource allocation issue in cros_ec_sensorhub.c.

----------------------------------------------------------------
Gwendal Grignou (1):
      platform/chrome: cros_ec_sensorhub: Allocate sensorhub resource before claiming sensors

 drivers/platform/chrome/cros_ec_sensorhub.c      | 80 ++++++++++++++----------
 drivers/platform/chrome/cros_ec_sensorhub_ring.c | 73 +++++++++++++--------
 include/linux/platform_data/cros_ec_sensorhub.h  |  1 +
 3 files changed, 93 insertions(+), 61 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 --]

             reply	other threads:[~2020-05-06 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 22:47 Benson Leung [this message]
2020-05-06 23:50 ` [GIT PULL] chrome-platform fixes for v5.7-rc5 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=20200506224737.GA159981@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.