From: Randy Dunlap <rdunlap@infradead.org>
To: Antonio Ospite <ospite@studenti.unina.it>, linux-kernel@vger.kernel.org
Cc: David Herrmann <dh.herrmann@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] Input: fix typos in Documentation/input/gamepad.txt
Date: Mon, 16 Dec 2013 11:18:02 -0800 [thread overview]
Message-ID: <52AF51EA.8090400@infradead.org> (raw)
In-Reply-To: <1387197292-29909-1-git-send-email-ospite@studenti.unina.it>
On 12/16/13 04:34, Antonio Ospite wrote:
> Fix some typos and while at it also use "PS" as the name for the central
> "HOME" button on Sony controllers, this is how Sony itself calls it.
>
> Signed-off-by: Antonio Ospite <ospite@studenti.unina.it>
> ---
> Documentation/input/gamepad.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/input/gamepad.txt b/Documentation/input/gamepad.txt
> index 4be7f21..63c0256 100644
> --- a/Documentation/input/gamepad.txt
> +++ b/Documentation/input/gamepad.txt
> @@ -71,7 +71,7 @@ features that you need, first. How each feature is mapped is described below.
> Legacy drivers often don't comply to these rules. As we cannot change them
> for backwards-compatibility reasons, you need to provide fixup mappings in
> user-space yourself. Some of them might also provide module-options that
> -change the mappings so you can adivce users to set these.
> +change the mappings so you can advice users to set these.
advise
>
> All new gamepads are supposed to comply with this mapping. Please report any
> bugs, if they don't.
--
~Randy
prev parent reply other threads:[~2013-12-16 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 12:34 [PATCH] Input: fix typos in Documentation/input/gamepad.txt Antonio Ospite
2013-12-16 13:03 ` David Herrmann
2013-12-16 15:10 ` Antonio Ospite
2013-12-16 19:18 ` Randy Dunlap [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=52AF51EA.8090400@infradead.org \
--to=rdunlap@infradead.org \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ospite@studenti.unina.it \
/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