All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	bleung@chromium.org, gregkh@linuxfoundation.org
Cc: bleung@google.com, bleung@chromium.org
Subject: [GIT PULL] chrome-platform updates for v4.20
Date: Wed, 31 Oct 2018 16:25:31 -0700	[thread overview]
Message-ID: <20181031232531.GA195672@google.com> (raw)

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

Hi Linus,

Please take a look at changes for chrome-platform for v4.20.

Note that there is another move from lee's to mine that we did as an IB.

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-for-v4.20

for you to fetch changes up to bc3f4b5c60db2a835e68bfdce23b6ae75df7e295:

  platform/chrome: chromeos_tbmc - Remove unneeded const (2018-10-09 22:40:12 -0700)

----------------------------------------------------------------
chrome-platform for v4.20

* Move mfd/cros_ec_lpc* includes to drivers/platform from mfd
* Adding a new interrupt path for cros_ec_lpc

----------------------------------------------------------------
Benson Leung (1):
      Merge remote-tracking branch 'origin/ib-chrome-platform-mfd-move-cros_ec_lpc' into working-branch-for-4.20

Emil Karlson (1):
      mfd: cros-ec: copy the whole event in get_next_event_xfer

Enric Balletbo i Serra (2):
      platform/chrome: Move mfd/cros_ec_lpc* includes to drivers/platform.
      mfd: cros_ec: Fix and improve kerneldoc comments.

Enrico Granata (1):
      platform/chrome: Add a new interrupt path for cros_ec_lpc

Nathan Chancellor (1):
      platform/chrome: chromeos_tbmc - Remove unneeded const

 drivers/mfd/cros_ec_dev.h                          |  13 +-
 drivers/platform/chrome/chromeos_tbmc.c            |   2 +-
 drivers/platform/chrome/cros_ec_lpc.c              |  18 +-
 drivers/platform/chrome/cros_ec_lpc_mec.c          |   3 +-
 .../platform/chrome}/cros_ec_lpc_mec.h             |   6 +-
 drivers/platform/chrome/cros_ec_lpc_reg.c          |   3 +-
 .../platform/chrome}/cros_ec_lpc_reg.h             |   6 +-
 drivers/platform/chrome/cros_ec_proto.c            |   2 +-
 include/linux/mfd/cros_ec.h                        | 214 ++++++++-------
 include/linux/mfd/cros_ec_commands.h               | 295 +++++++++++++--------
 10 files changed, 338 insertions(+), 224 deletions(-)
 rename {include/linux/mfd => drivers/platform/chrome}/cros_ec_lpc_mec.h (96%)
 rename {include/linux/mfd => drivers/platform/chrome}/cros_ec_lpc_reg.h (94%)


 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:[~2018-10-31 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 23:25 Benson Leung [this message]
2018-10-31 23:50 ` [GIT PULL] chrome-platform updates for v4.20 Linus Torvalds

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=20181031232531.GA195672@google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --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.