From: "Heiko Stübner" <heiko@sntech.de>
To: Luis Ortega <luiorpe1@upv.es>
Cc: dmitry.torokhov@gmail.com, yongjun_wei@trendmicro.com.cn,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Input: zforce - fix spelling errors
Date: Mon, 27 Jan 2014 19:41:52 +0100 [thread overview]
Message-ID: <1778950.Yzcf1IeZVD@phil> (raw)
In-Reply-To: <1390848373-7723-2-git-send-email-luiorpe1@upv.es>
On Monday, 27. January 2014 19:46:10 Luis Ortega wrote:
> Fixed a few spelling errors.
>
> Signed-off-by: Luis Ortega <luiorpe1@upv.es>
Acked-by: Heiko Stuebner <heiko@sntech.de>
> ---
> drivers/input/touchscreen/zforce_ts.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/input/touchscreen/zforce_ts.c
> b/drivers/input/touchscreen/zforce_ts.c index 2175f34..c145c1d 100644
> --- a/drivers/input/touchscreen/zforce_ts.c
> +++ b/drivers/input/touchscreen/zforce_ts.c
> @@ -64,7 +64,7 @@
> #define RESPONSE_STATUS 0X1e
>
> /*
> - * Notifications are send by the touch controller without
> + * Notifications are sent by the touch controller without
> * being requested by the driver and include for example
> * touch indications
> */
> @@ -103,8 +103,8 @@ struct zforce_point {
> * @suspended device suspended
> * @access_mutex serialize i2c-access, to keep multipart reads together
> * @command_done completion to wait for the command result
> - * @command_mutex serialize commands send to the ic
> - * @command_waiting the id of the command that that is currently waiting
> + * @command_mutex serialize commands sent to the ic
> + * @command_waiting the id of the command that is currently waiting
> * for a result
> * @command_result returned result of the command
> */
> @@ -332,7 +332,7 @@ static int zforce_touch_event(struct zforce_ts *ts, u8
> *payload)
>
> count = payload[0];
> if (count > ZFORCE_REPORT_POINTS) {
> - dev_warn(&client->dev, "to many coordinates %d, expected max %d\n",
> + dev_warn(&client->dev, "too many coordinates %d, expected max %d\n",
> count, ZFORCE_REPORT_POINTS);
> count = ZFORCE_REPORT_POINTS;
> }
> @@ -798,7 +798,7 @@ static int zforce_probe(struct i2c_client *client,
> return ret;
> }
>
> - /* this gets the firmware version among other informations */
> + /* this gets the firmware version among other information */
> ret = zforce_command_wait(ts, COMMAND_STATUS);
> if (ret < 0) {
> dev_err(&client->dev, "couldn't get status, %d\n", ret);
next prev parent reply other threads:[~2014-01-27 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 18:46 Input: zforce - fix various small issues Luis Ortega
2014-01-27 18:46 ` [PATCH 1/4] Input: zforce - fix spelling errors Luis Ortega
2014-01-27 18:41 ` Heiko Stübner [this message]
2014-01-27 18:46 ` [PATCH 2/4] Input: zforce - fix lines exceeding 80 columns Luis Ortega
2014-01-27 19:12 ` Heiko Stübner
2014-01-27 19:29 ` Luis Ortega
2014-01-27 18:46 ` [PATCH 3/4] Input: zforce - Remove unnecessary payload data checks Luis Ortega
2014-01-27 20:16 ` Heiko Stübner
2014-01-27 18:46 ` [PATCH 4/4] Input: zforce - reduce stack memory allocated to frames Luis Ortega
2014-01-27 20:22 ` Heiko Stübner
2014-01-28 6:44 ` Input: zforce - fix various small issues Dmitry Torokhov
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=1778950.Yzcf1IeZVD@phil \
--to=heiko@sntech.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiorpe1@upv.es \
--cc=yongjun_wei@trendmicro.com.cn \
/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).