All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "Marcos Paulo de Souza" <marcos.souza.org@gmail.com>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Ben Gamari" <ben@smart-cactus.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Input: ALPS: fix protcol -> protocol
Date: Mon, 12 Dec 2016 07:53:54 -0200	[thread overview]
Message-ID: <20161212095442.2391-1-marcos.souza.org@gmail.com> (raw)

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
-- 
2.9.3

WARNING: multiple messages have this Message-ID (diff)
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: "Marcos Paulo de Souza" <marcos.souza.org@gmail.com>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Ben Gamari" <ben@smart-cactus.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Input: ALPS: fix protcol -> protocol
Date: Mon, 12 Dec 2016 07:53:54 -0200	[thread overview]
Message-ID: <20161212095442.2391-1-marcos.souza.org@gmail.com> (raw)

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
-- 
2.9.3


             reply	other threads:[~2016-12-12  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  9:53 Marcos Paulo de Souza [this message]
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

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=20161212095442.2391-1-marcos.souza.org@gmail.com \
    --to=marcos.souza.org@gmail.com \
    --cc=ben@smart-cactus.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.