From: Lee Jones <lee.jones@linaro.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, gwendal@chromium.org,
jflat@chromium.org, kernel@collabora.com, bleung@chromium.org,
groeck@chromium.org, rajatja@google.com, dtor@chromium.org
Subject: Re: [PATCH v2 2/2] mfd: cros_ec: Instantiate the CrOS USB PD logger driver
Date: Thu, 4 Apr 2019 09:12:58 +0100 [thread overview]
Message-ID: <20190404081258.GL6830@dell> (raw)
In-Reply-To: <20190403140529.23103-2-enric.balletbo@collabora.com>
On Wed, 03 Apr 2019, Enric Balletbo i Serra wrote:
> Add the cros-usbpd-logger driver for logging event data for the USB PD
> charger available in the Embedded Controller on ChromeOS systems. The
> logging feature is logically separate functionality from charge manager,
> hence is instantiated as a different driver.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> Lee, this is send as separate patch because touches the MFD subsystem,
> apart from that the driver won't be instantiated if [1/2] is not
> merged, which I think is not a problem, it is safe for both go through
> their subsystem separately.
>
> Thanks,
> Enric
>
> Changes in v2: None
>
> drivers/mfd/cros_ec_dev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied, thanks.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-04-04 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:05 [PATCH v2 1/2] platform/chrome: Add CrOS USB PD logging driver Enric Balletbo i Serra
2019-04-03 14:05 ` [PATCH v2 2/2] mfd: cros_ec: Instantiate the CrOS USB PD logger driver Enric Balletbo i Serra
2019-04-03 16:35 ` Guenter Roeck
2019-04-04 8:12 ` Lee Jones [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=20190404081258.GL6830@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=dtor@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jflat@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rajatja@google.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 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).