From: Lee Jones <lee.jones@linaro.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Russell King <linux@armlinux.org.uk>,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Benson Leung <bleung@chromium.org>,
Olof Johansson <olof@lixom.net>,
Gwendal Grignou <gwendal@chromium.org>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
kernel@collabora.com, Guenter Roeck <groeck@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] platform/chrome: Move cros-ec transport drivers to drivers/platform.
Date: Tue, 3 Jul 2018 07:32:30 +0100 [thread overview]
Message-ID: <20180703063230.GC4242@dell> (raw)
In-Reply-To: <20180702102201.13461-2-enric.balletbo@collabora.com>
On Mon, 02 Jul 2018, Enric Balletbo i Serra wrote:
> There are some cros-ec transport drivers (I2C, SPI) living in MFD, while
> others (LPC) living in drivers/platform. The transport drivers are more
> platform specific. So, move the I2C and SPI transport drivers to the
> platform/chrome directory. The patch also removes the MFD_ prefix of
> their Kconfig symbols.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
>
> drivers/mfd/Kconfig | 20 -------------------
> drivers/mfd/Makefile | 2 --
> drivers/platform/chrome/Kconfig | 20 +++++++++++++++++++
> drivers/platform/chrome/Makefile | 2 ++
> .../{mfd => platform/chrome}/cros_ec_i2c.c | 0
> .../{mfd => platform/chrome}/cros_ec_spi.c | 0
> 6 files changed, 22 insertions(+), 22 deletions(-)
> rename drivers/{mfd => platform/chrome}/cros_ec_i2c.c (100%)
> rename drivers/{mfd => platform/chrome}/cros_ec_spi.c (100%)
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] platform/chrome: Move cros-ec transport drivers to drivers/platform.
Date: Tue, 3 Jul 2018 07:32:30 +0100 [thread overview]
Message-ID: <20180703063230.GC4242@dell> (raw)
In-Reply-To: <20180702102201.13461-2-enric.balletbo@collabora.com>
On Mon, 02 Jul 2018, Enric Balletbo i Serra wrote:
> There are some cros-ec transport drivers (I2C, SPI) living in MFD, while
> others (LPC) living in drivers/platform. The transport drivers are more
> platform specific. So, move the I2C and SPI transport drivers to the
> platform/chrome directory. The patch also removes the MFD_ prefix of
> their Kconfig symbols.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
>
> drivers/mfd/Kconfig | 20 -------------------
> drivers/mfd/Makefile | 2 --
> drivers/platform/chrome/Kconfig | 20 +++++++++++++++++++
> drivers/platform/chrome/Makefile | 2 ++
> .../{mfd => platform/chrome}/cros_ec_i2c.c | 0
> .../{mfd => platform/chrome}/cros_ec_spi.c | 0
> 6 files changed, 22 insertions(+), 22 deletions(-)
> rename drivers/{mfd => platform/chrome}/cros_ec_i2c.c (100%)
> rename drivers/{mfd => platform/chrome}/cros_ec_spi.c (100%)
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [???]
Linaro Services Technical Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-07-03 6:32 UTC|newest]
Thread overview: 31+ 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 ` Enric Balletbo i Serra
2018-07-02 10:21 ` Enric Balletbo i Serra
2018-07-02 10:21 ` [PATCH 1/3] platform/chrome: " Enric Balletbo i Serra
2018-07-02 10:21 ` Enric Balletbo i Serra
2018-07-02 14:39 ` Guenter Roeck
2018-07-02 14:39 ` Guenter Roeck
2018-07-03 6:32 ` Lee Jones [this message]
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 10:22 ` Enric Balletbo i Serra
2018-07-02 10:22 ` Enric Balletbo i Serra
2018-07-02 11:05 ` Krzysztof Kozlowski
2018-07-02 11:05 ` Krzysztof Kozlowski
2018-07-02 11:05 ` Krzysztof Kozlowski
2018-07-02 23:02 ` Benson Leung
2018-07-02 23:02 ` Benson Leung
2018-07-02 23:02 ` Benson Leung
2018-07-03 6:33 ` Lee Jones
2018-07-03 6:33 ` Lee Jones
2018-07-03 6:33 ` Lee Jones
2018-07-02 14:42 ` Guenter Roeck
2018-07-02 14:42 ` Guenter Roeck
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 10:22 ` Enric Balletbo i Serra
2018-07-02 14:43 ` Guenter Roeck
2018-07-02 14:43 ` Guenter Roeck
2018-07-02 23:13 ` [PATCH 0/3] platform/chrome: mfd: Move cros-ec transport drivers to drivers/platform Benson Leung
2018-07-02 23:13 ` Benson Leung
2018-07-02 23:13 ` Benson Leung
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=20180703063230.GC4242@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@google.com \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
--cc=will.deacon@arm.com \
/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.