linux-kernel - [PATCH 0/3] platform/chrome: Changes for cros_ec_lpc and cros_ec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 May 2015 10:39:04 +0200
From:	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To:	Olof Johansson <olof@...om.net>
Cc:	Doug Anderson <dianders@...omium.org>,
	Gwendal Grignou <gwendal@...gle.com>,
	Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Subject: [PATCH 0/3] platform/chrome: Changes for cros_ec_lpc and cros_ec_dev

Hello Olof,

This series contain a fix and a cleanup for the cros_ec_lpc driver and
a small fix for cros_ec_dev driver. The first two patches were posted
as a part of the "mfd: cros_ec: Add multi EC and proto v3 support" [0]
series but I split it since there isn't really a dependency and you can
pick these through your chrome-platform tree.

The last patch was posted a week ago [1] but I'm resending here to make
it easier for you to pick all the pending patches.

Javier Martinez Canillas (3):
  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

 drivers/platform/chrome/cros_ec_dev.c |  6 ++++++
 drivers/platform/chrome/cros_ec_lpc.c | 21 +++++++++------------
 2 files changed, 15 insertions(+), 12 deletions(-)

Best regards,
Javier

[0]: https://lkml.org/lkml/2015/5/9/73
[1]: https://lkml.org/lkml/2015/5/13/1023

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/