All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: bleung@chromium.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, enric.balletbo@collabora.com
Cc: bleung@google.com
Subject: [GIT PULL] chrome-platform updates for v4.21
Date: Fri, 4 Jan 2019 06:53:10 -0800	[thread overview]
Message-ID: <20190104145310.GA83219@google.com> (raw)

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

Hi Linus,

Happy new year. Sorry for the late in the window pull request, but here are
the updates for chrome-platform.

Mainly a maintainership change, and a pair of patches from Brian to fixup
wakeup handling for one kind of EC event.


The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/tag-chrome-platform-for-v4.21

for you to fetch changes up to cdd6a4a0e2ec590c30ad0e965fa08bf37461cadb:

  MAINTAINERS: add maintainers for ChromeOS EC sub-drivers (2019-01-03 12:26:43 -0800)

----------------------------------------------------------------
chrome platform changes for v4.21

Changes for EC_MKBP_EVENT_SENSOR_FIFO handling.
Also, maintainership changes. Olofj out, Enric balletbo in.

----------------------------------------------------------------
Benson Leung (1):
      MAINTAINERS: platform/chrome: Add Enric as a maintainer

Brian Norris (2):
      platform/chrome: straighten out cros_ec_get_{next,host}_event() error codes
      platform/chrome: don't report EC_MKBP_EVENT_SENSOR_FIFO as wakeup

Enric Balletbo i Serra (1):
      MAINTAINERS: add maintainers for ChromeOS EC sub-drivers

Olof Johansson (1):
      MAINTAINERS: platform/chrome: remove myself as maintainer

 MAINTAINERS                             | 11 ++++++++++-
 drivers/platform/chrome/cros_ec_proto.c | 22 +++++++++++++++++-----
 include/linux/mfd/cros_ec.h             |  6 ++++--
 3 files changed, 31 insertions(+), 8 deletions(-)

Thanks,
Benson

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

             reply	other threads:[~2019-01-04 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 14:53 Benson Leung [this message]
2019-01-06 20:20 ` [GIT PULL] chrome-platform updates for v4.21 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=20190104145310.GA83219@google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.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.