From: Lee Jones <lee.jones@linaro.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-kernel@vger.kernel.org,
"Sameer Nanda" <snanda@chromium.org>,
"Benson Leung" <bleung@chromium.org>,
"Enric Balletbò" <enric.balletbo@collabora.co.uk>,
"Vic Yang" <victoryang@chromium.org>,
"Vincent Palatin" <vpalatin@chromium.org>,
"Randall Spangler" <rspangler@chromium.org>,
"Gwendal Grignou" <gwendal@chromium.org>
Subject: Re: [PATCH v1 1/6] mfd: cros_ec: small kerneldoc fix
Date: Wed, 10 Feb 2016 16:25:14 +0000 [thread overview]
Message-ID: <20160210162514.GK3782@x1> (raw)
In-Reply-To: <1454679181-8949-2-git-send-email-tomeu.vizoso@collabora.com>
On Fri, 05 Feb 2016, Tomeu Vizoso wrote:
> s/cros_ec_register/cros_ec_query_all
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> ---
>
> include/linux/mfd/cros_ec.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/mfd/cros_ec.h b/include/linux/mfd/cros_ec.h
> index 494682ce4bf3..a677c2bd485c 100644
> --- a/include/linux/mfd/cros_ec.h
> +++ b/include/linux/mfd/cros_ec.h
> @@ -245,7 +245,7 @@ int cros_ec_remove(struct cros_ec_device *ec_dev);
> int cros_ec_register(struct cros_ec_device *ec_dev);
>
> /**
> - * cros_ec_register - Query the protocol version supported by the ChromeOS EC
> + * cros_ec_query_all - Query the protocol version supported by the ChromeOS EC
> *
> * @ec_dev: Device to register
> * @return 0 if ok, -ve on error
I'll fix the subject line for you this time.
In future please submit using the format set by the subsystem.
`git log --oneline -- <subsystem>` helps with this.
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-02-10 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:32 [PATCH v1 0/6] EC-based USB Power Delivery support for Chrome machines Tomeu Vizoso
2016-02-05 13:32 ` [PATCH v1 1/6] mfd: cros_ec: small kerneldoc fix Tomeu Vizoso
2016-02-05 18:46 ` Benson Leung
2016-02-10 16:25 ` Lee Jones [this message]
2016-02-05 13:32 ` [PATCH v1 2/6] mfd: cros_ec: Add MKBP event support Tomeu Vizoso
2016-02-10 17:41 ` Gwendal Grignou
2016-02-11 9:15 ` Lee Jones
[not found] ` <CAMHSBOXRvC7U_KWeg+rX3Qymaos0-3FN6AuaXT2cyP=gAN47mA@mail.gmail.com>
2016-02-11 14:52 ` Tomeu Vizoso
2016-02-11 18:49 ` Gwendal Grignou
2016-02-05 13:32 ` [PATCH v1 3/6] power_supply: Add types for USB Type C and PD chargers Tomeu Vizoso
2016-02-05 18:38 ` Benson Leung
2016-02-11 10:00 ` Tomeu Vizoso
2016-02-11 15:05 ` Benson Leung
2016-02-05 13:32 ` [PATCH v1 4/6] power: cros_usbpd-charger: Add EC-based USB PD charger driver Tomeu Vizoso
2016-02-10 16:49 ` Lee Jones
2016-02-12 11:07 ` Tomeu Vizoso
2016-02-05 13:33 ` [PATCH v1 5/6] platform/chrome: Register USB PD charger device Tomeu Vizoso
2016-02-10 16:46 ` Lee Jones
2016-02-12 11:06 ` Tomeu Vizoso
2016-02-05 13:33 ` [PATCH v1 6/6] platform/chrome: Check the USB PD feature before creating a charger Tomeu Vizoso
2016-02-10 16:28 ` Lee Jones
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=20160210162514.GK3782@x1 \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.co.uk \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rspangler@chromium.org \
--cc=snanda@chromium.org \
--cc=tomeu.vizoso@collabora.com \
--cc=victoryang@chromium.org \
--cc=vpalatin@chromium.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