The following changes since commit 3eb2ce825ea1ad89d20f7a3b5780df850e4be274:
Linux 4.16-rc7 (2018-03-25 12:44:30 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/chrome-platform-for-linus-4.17
for you to fetch changes up to c171d3b8a67e08884d915ffbb1dbc475747d7df2:
Merge remote-tracking branch 'origin/ib-chrome-platform-cros-ec-sysfs-debugfs-for-v4.17' into working-branch-for-4.17 (2018-04-10 22:30:34 -0700)
----------------------------------------------------------------
Changes to chrome-platform for v4.17
Incorporates a series from Dmitry to remove platform data from
chromeos_laptop.c, which was the only user of platform data
for the atmel_mxt_ts driver.
Includes a series to clean up sysfs and debugfs for cros_ec.
Other misc. cleanups.
Thanks,
Benson
----------------------------------------------------------------
Benson Leung (2):
Merge remote-tracking branch 'chrome-platform-stop-being-a-platform-driver-plus-atmel_mxt_ts-for-v4.17' into working-branch-for-4.17
Merge remote-tracking branch 'origin/ib-chrome-platform-cros-ec-sysfs-debugfs-for-v4.17' into working-branch-for-4.17
Dmitry Torokhov (14):
Input: atmel_mxt_ts - do not pass suspend mode in platform data
Input: atmel_mxt_ts - switch from OF to generic device properties
Input: atmel_mxt_ts - switch ChromeOS ACPI devices to generic props
platform/chrome: chromeos_laptop - add SPDX identifier
platform/chrome: chromeos_laptop - stop setting suspend mode for Atmel devices
platform/chrome: chromeos_laptop - introduce pr_fmt()
platform/chrome: chromeos_laptop - factor out getting IRQ from DMI
platform/chrome: chromeos_laptop - rework i2c peripherals initialization
platform/chrome: chromeos_laptop - parse DMI IRQ data once
platform/chrome: chromeos_laptop - use I2C notifier to create devices
platform/chrome: chromeos_laptop - rely on I2C to set up interrupt trigger
platform/chrome: chromeos_laptop - use device properties for Pixel
platform/chrome: chromeos_laptop - discard data for unneeded boards
Input: atmel_mxt_ts - remove platform data support
Enric Balletbo i Serra (3):
platform/chrome: cros_ec_sysfs: introduce to_cros_ec_dev define.
platform/chrome: cros_ec_sysfs: use permission-specific DEVICE_ATTR variants
platform/chrome: cros_ec_debugfs: Use octal permissions '0444'
Gwendal Grignou (2):
platform/chrome: cros_ec_sysfs: Modify error handling
platform/chrome: mfd/cros_ec_dev: Add sysfs entry to set keyboard wake lid angle
Salvatore Bellizzi (1):
platform/chrome: cros_ec_lpc: Add support for Google devices using custom coreboot firmware
Shawn Nematbakhsh (1):
platform/chrome: cros_ec_debugfs: Add PD port info to debugfs
Wenkai Du (1):
platform/chrome: cros_ec_lpc: wake up from s2idle on Chrome EC
MAINTAINERS | 1 -
drivers/input/touchscreen/atmel_mxt_ts.c | 231 ++++----
drivers/mfd/cros_ec_dev.c | 31 +-
drivers/platform/chrome/chromeos_laptop.c | 896 +++++++++++++++--------------
drivers/platform/chrome/cros_ec_debugfs.c | 76 ++-
drivers/platform/chrome/cros_ec_lpc.c | 16 +
drivers/platform/chrome/cros_ec_sysfs.c | 141 +++--
include/linux/mfd/cros_ec.h | 2 +
include/linux/mfd/cros_ec_commands.h | 3 +
include/linux/platform_data/atmel_mxt_ts.h | 31 -
10 files changed, 789 insertions(+), 639 deletions(-)
delete mode 100644 include/linux/platform_data/atmel_mxt_ts.h
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
[email protected]
Chromium OS Project
[email protected]
On Thu, Apr 12, 2018 at 3:21 PM, Benson Leung <[email protected]> wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/chrome-platform-for-linus-4.17
Please don't do this to me.
You're sending me a pull request in the second half of the second week
of the merge window, and none of this has been in linux-next as far as
I can tell.
I don't even check linux-next as of when the merge window opened - I
check it as of "one week into the merge window".
Ok, ok, I do in fact find two of the commits in linux-next, but even
they have been rebased for some reason.
The others? I can't find them even in some rebased form.
I'll take this for now, but next time I see this kind of "late in the
merge window, absolutely zero exposure anywhere else", I'll just skip
the whole pull request. Don't do it.
Linus
On Fri, Apr 13, 2018 at 04:26:41PM -0700, Linus Torvalds wrote:
> Please don't do this to me.
>
> You're sending me a pull request in the second half of the second week
> of the merge window, and none of this has been in linux-next as far as
> I can tell.
>
> I don't even check linux-next as of when the merge window opened - I
> check it as of "one week into the merge window".
>
> Ok, ok, I do in fact find two of the commits in linux-next, but even
> they have been rebased for some reason.
>
> The others? I can't find them even in some rebased form.
>
> I'll take this for now, but next time I see this kind of "late in the
> merge window, absolutely zero exposure anywhere else", I'll just skip
> the whole pull request. Don't do it.
Sorry about that, Linus. Won't happen again.
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
[email protected]
Chromium OS Project
[email protected]