From: bleung@google.com (Benson Leung)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] platform/chrome: mfd: Move cros-ec transport drivers to drivers/platform
Date: Mon, 2 Jul 2018 16:13:18 -0700 [thread overview]
Message-ID: <20180702231318.GB86110@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <20180702102201.13461-1-enric.balletbo@collabora.com>
Hi Enric,
On Mon, Jul 02, 2018 at 12:21:58PM +0200, Enric Balletbo i Serra wrote:
> Hi,
>
> The cros-ec transport drivers are placed in two subsystems, in MFD and
> in platform/chrome. As far as I know there is no reason for this, so,
> move the I2C and the SPI cros-ec transport driver from the MFD subsystem
> to the platform/chrome. The series also removes the MFD_ prefix for the
> Kconfig symbols, modifies the defconfigs that used these symbols and
> fixes the KEYBOARD_CROS_EC Kconfig help.
>
Thanks for putting this together.
I can create an IB with this for the others to pull. What do you all think?
Thanks,
Benson
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung at google.com
Chromium OS Project
bleung at chromium.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180702/20877326/attachment.sig>
prev parent reply other threads:[~2018-07-02 23:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 10:21 [PATCH 0/3] platform/chrome: mfd: Move cros-ec transport drivers to drivers/platform Enric Balletbo i Serra
2018-07-02 10:21 ` [PATCH 1/3] platform/chrome: " Enric Balletbo i Serra
2018-07-02 14:39 ` Guenter Roeck
2018-07-03 6:32 ` Lee Jones
2018-07-02 10:22 ` [PATCH 2/3] arm/arm64: configs: Remove the MFD_ prefix for MFD_CROS_EC_I2C/SPI symbols Enric Balletbo i Serra
2018-07-02 11:05 ` Krzysztof Kozlowski
2018-07-02 23:02 ` Benson Leung
2018-07-03 6:33 ` Lee Jones
2018-07-02 14:42 ` Guenter Roeck
2018-07-02 10:22 ` [PATCH 3/3] Input: keyboard: Fix ChromeOS EC keyboard help message Enric Balletbo i Serra
2018-07-02 14:43 ` Guenter Roeck
2018-07-02 23:13 ` Benson Leung [this message]
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=20180702231318.GB86110@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).