From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
Ben Gamari <ben@smart-cactus.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: ALPS: fix protcol -> protocol
Date: Mon, 12 Dec 2016 11:01:21 -0800 [thread overview]
Message-ID: <20161212190121.GA10591@dtor-ws> (raw)
In-Reply-To: <20161212095608.GA18387@pali>
On Mon, Dec 12, 2016 at 10:56:08AM +0100, Pali Rohár wrote:
> On Monday 12 December 2016 07:53:54 Marcos Paulo de Souza wrote:
> > Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
> > ---
> > drivers/input/mouse/alps.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/mouse/alps.h b/drivers/input/mouse/alps.h
> > index b9417e2..50f05a7 100644
> > --- a/drivers/input/mouse/alps.h
> > +++ b/drivers/input/mouse/alps.h
> > @@ -146,7 +146,7 @@ struct alps_protocol_info {
> > * (aka command mode response) identifies the firmware minor version. This
> > * can be used to distinguish different hardware models which are not
> > * uniquely identifiable through their E7 responses.
> > - * @protocol_info: information about protcol used by the device.
> > + * @protocol_info: information about protocol used by the device.
> > *
> > * Many (but not all) ALPS touchpads can be identified by looking at the
> > * values returned in the "E7 report" and/or the "EC report." This table
>
> Thanks! Add my Reviewed-by: Pali Rohár <pali.rohar@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2016-12-12 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 9:53 [PATCH] Input: ALPS: fix protcol -> protocol Marcos Paulo de Souza
2016-12-12 9:56 ` Pali Rohár
2016-12-12 19:01 ` Dmitry Torokhov [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=20161212190121.GA10591@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=ben@smart-cactus.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=pali.rohar@gmail.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).