From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: patches@lists.linux.dev, Randy Dunlap <rdunlap@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Docs: correct atarikbd.rst typos
Date: Tue, 17 May 2022 13:29:30 -0600 [thread overview]
Message-ID: <87y1z0ufdx.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220516002055.12000-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Fix 2 "MOSE" typos in atarikbd.rst (found with 'codespell').
> a. s/MOSE/MODE/
> b. s/MOSE/MOUSE/
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: linux-input@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> ---
> Documentation/input/devices/atarikbd.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- a/Documentation/input/devices/atarikbd.rst
> +++ b/Documentation/input/devices/atarikbd.rst
> @@ -288,7 +288,7 @@ between 0 and large positive numbers. Ex
> command sets the maximum positive value that can be attained in the scaled
> coordinate system. Motion beyond that value is also ignored.
>
> -SET MOUSE KEYCODE MOSE
> +SET MOUSE KEYCODE MODE
> ----------------------
>
> ::
> @@ -333,7 +333,7 @@ occur before the internally maintained c
> (independently scaled for each axis). Remember that the mouse position
> information is available only by interrogating the ikbd in the ABSOLUTE MOUSE
> POSITIONING mode unless the ikbd has been commanded to report on button press
> -or release (see SET MOSE BUTTON ACTION).
> +or release (see SET MOUSE BUTTON ACTION).
>
Applied, thanks.
jon
prev parent reply other threads:[~2022-05-17 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 0:20 [PATCH] input: Docs: correct atarikbd.rst typos Randy Dunlap
2022-05-17 19:29 ` Jonathan Corbet [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=87y1z0ufdx.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).