public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: olof@lixom.net, linux-kernel@vger.kernel.org
Subject: [GIT PULL] platform/chrome: Changes for 4.4
Date: Fri, 13 Nov 2015 21:19:51 -0800	[thread overview]
Message-ID: <20151114051951.GA13156@localhost> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 2677 bytes --]

Hi Linus,

Chrome hardware platform changes for 4.4. Please merge.


Thanks!

-Olof


The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46:

  Linux 4.3-rc4 (2015-10-04 16:57:17 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform.git tags/chrome-platform-4.4

for you to fetch changes up to ebaf31c46cce0dc8a6ed690b5456b295aa7586a6:

  platform/chrome: Fix i2c-designware adapter name (2015-11-09 19:43:33 -0800)

----------------------------------------------------------------
platform/chrome: Branch for v4.4

Here's the branch of chrome platform changes for v4.4. Some have been queued
up for the full 4.3 release cycle since I forgot to send them in for that
round (rebased early on to deal with fixes conflicts).

Most of these enable EC communication stuff -- Pixel 2015 support, enabling
building for ARM64 platforms, and a few fixes for memory leaks.

There's also a patch in here to allow reading/writing the verified boot
context, which depends on a sysfs patch acked by Greg.

----------------------------------------------------------------
Christian Engelmayer (2):
      platform/chrome: cros_ec: Fix leak in sequence_store()
      platform/chrome: cros_ec: Fix possible leak in led_rgb_store()

Emilio López (2):
      sysfs: Support is_visible() on binary attributes
      platform/chrome: Support reading/writing the vboot context

Jarkko Nikula (1):
      platform/chrome: Fix i2c-designware adapter name

Javier Martinez Canillas (5):
      Revert "platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM"
      platform/chrome: Make depends on MFD_CROS_EC instead CROS_EC_PROTO
      platform/chrome: cros_ec_lpc - Use existing function to check EC result
      platform/chrome: cros_ec_lpc - Add support for Google Pixel 2
      platform/chrome: cros_ec_dev - Add a platform device ID table

Thierry Reding (1):
      platform/chrome: Enable Chrome platforms on 64-bit ARM

 drivers/platform/chrome/Kconfig            |   5 +-
 drivers/platform/chrome/Makefile           |   3 +-
 drivers/platform/chrome/chromeos_laptop.c  |   4 +-
 drivers/platform/chrome/cros_ec_dev.c      |   7 ++
 drivers/platform/chrome/cros_ec_lightbar.c |  31 ++++---
 drivers/platform/chrome/cros_ec_lpc.c      |  21 ++---
 drivers/platform/chrome/cros_ec_vbc.c      | 137 +++++++++++++++++++++++++++++
 fs/sysfs/group.c                           |  17 +++-
 include/linux/mfd/cros_ec.h                |   1 +
 include/linux/sysfs.h                      |  18 +++-
 10 files changed, 207 insertions(+), 37 deletions(-)
 create mode 100644 drivers/platform/chrome/cros_ec_vbc.c

                 reply	other threads:[~2015-11-14  5:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151114051951.GA13156@localhost \
    --to=olof@lixom.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox