From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
enric.balletbo@collabora.com
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org, bleung@google.com
Subject: [GIT PULL] chrome-platform updates for v5.1
Date: Mon, 11 Mar 2019 21:39:08 -0700 [thread overview]
Message-ID: <20190312043908.GA261883@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]
Hi Linus,
The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:
Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-for-v5.1
for you to fetch changes up to 2794449576a6024e203eca5cc2c1a3ae33102b8e:
platform/chrome: fix wilco-ec dependencies (2019-03-05 11:35:46 +0100)
----------------------------------------------------------------
chrome platform changes for v5.1
1. SPDX identifier cleanup for platform/chrome
2. Cleanup series between mfd and chrome/platform, moving
cros-ec attributes from mfd/cros_ec_dev to sub-drivers in platform/chrome.
3. Wilco EC driver
4. Maintainership change to new group repository.
----------------------------------------------------------------
Arnd Bergmann (1):
platform/chrome: fix wilco-ec dependencies
Enric Balletbo i Serra (20):
mfd / platform: cros_ec: Use devm_mfd_add_devices
mfd / platform: cros_ec: Move lightbar attributes to its own driver
mfd / platform: cros_ec: Move vbc attributes to its own driver
mfd / platform: cros_ec: Move debugfs attributes to its own driver
mfd / platform: cros_ec: Move device sysfs attributes to its own driver
mfd / platform: cros_ec_vbc: Instantiate only if the EC has a VBC NVRAM
platform/chrome: cros_ec_lightbar: Instantiate only if the EC has a lightbar
platform/chrome: cromeos_pstore: switch to SPDX identifier
platform/chrome: cros_ec_debugfs: switch to SPDX identifier
platform/chrome: cros_ec_lightbar: switch to SPDX identifier
platform/chrome: cros_ec_sysfs: switch to SPDX identifier
platform/chrome: cros_ec_vbc: switch to SPDX identifier
platform/chrome: cros_ec_i2c: switch to SPDX identifier
platform/chrome: cros_ec_lpc: switch to SPDX identifier
platform/chrome: cros_ec_proto: switch to SPDX identifier
platform/chrome: cros_ec_spi: switch to SPDX identifier
platform/chrome: cros_kbd_led_backlight: switch to SPDX identifier
platform/chrome: cros_ec_lightbar: remove pr_fmt() define
platform/chrome: cros_ec_sysfs: remove pr_fmt() define
MAINTAINERS: chrome-platform: change the git tree to a chrome-platform group git tree
Nick Crews (4):
platform/chrome: cros_ec: Remove cros_ec dependency in lpc_mec
platform/chrome: Add new driver for Wilco EC
Thank you,
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:[~2019-03-12 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 4:39 Benson Leung [this message]
2019-03-12 16:56 ` [GIT PULL] chrome-platform updates for v5.1 Linus Torvalds
2019-03-12 17:52 ` Benson Leung
2019-03-12 17:00 ` 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=20190312043908.GA261883@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.