From: Benson Leung <bleung@google.com>
To: lee.jones@linaro.org, dmitry.torokhov@gmail.com, linux@armlinux.org.uk
Cc: bleung@chromium.org, enric.balletbo@collabora.com,
krzk@kernel.org, linux-kernel@vger.kernel.org, bleung@google.com
Subject: [GIT PULL] Immutable branch (mfd, chrome) due for the v4.19 window
Date: Sun, 8 Jul 2018 18:13:24 -0700 [thread overview]
Message-ID: <20180709011324.GA86474@decatoncale.mtv.corp.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]
Hi all,
Please see this Immutable Branch which moves the cros_ec_i2c and cros_ec_spi
transport drivers from mfd to platform/chrome. Changes in arm are a simple
rename in defconfigs. Change in input is a rename in help text.
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/ib-platform-chrome-mfd-move-cros-ec-transport-for-4.19
for you to fetch changes up to 413c94469a9db26ac4e1d16bf8de0248de93e2d8:
Input: keyboard: Fix ChromeOS EC keyboard help message. (2018-07-03 12:40:44 -0700)
----------------------------------------------------------------
Immutable branch (mfd, chrome) due for the v4.19 window
Immutable Branch which moves the cros_ec_i2c and cros_ec_spi
transport drivers from mfd to platform/chrome. Changes in arm are a simple
rename in defconfigs. Change in input is a rename in help text.
----------------------------------------------------------------
Enric Balletbo i Serra (3):
platform/chrome: Move cros-ec transport drivers to drivers/platform.
arm/arm64: configs: Remove the MFD_ prefix for MFD_CROS_EC_I2C/SPI symbols.
Input: keyboard: Fix ChromeOS EC keyboard help message.
arch/arm/configs/exynos_defconfig | 4 ++--
arch/arm/configs/multi_v7_defconfig | 4 ++--
arch/arm/configs/pxa_defconfig | 4 ++--
arch/arm64/configs/defconfig | 4 ++--
drivers/input/keyboard/Kconfig | 2 +-
drivers/mfd/Kconfig | 20 --------------------
drivers/mfd/Makefile | 2 --
drivers/platform/chrome/Kconfig | 20 ++++++++++++++++++++
drivers/platform/chrome/Makefile | 2 ++
drivers/{mfd => platform/chrome}/cros_ec_i2c.c | 0
drivers/{mfd => platform/chrome}/cros_ec_spi.c | 0
11 files changed, 31 insertions(+), 31 deletions(-)
rename drivers/{mfd => platform/chrome}/cros_ec_i2c.c (100%)
rename drivers/{mfd => platform/chrome}/cros_ec_spi.c (100%)
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 --]
next reply other threads:[~2018-07-09 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 1:13 Benson Leung [this message]
2018-07-27 7:13 ` [GIT PULL] Immutable branch (mfd, chrome) due for the v4.19 window Lee Jones
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=20180709011324.GA86474@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).