From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH 8/8] input: Documentation: corrections for uinput.rst
Date: Tue, 2 Mar 2021 14:35:23 -0800 [thread overview]
Message-ID: <20210302223523.20130-9-rdunlap@infradead.org> (raw)
In-Reply-To: <20210302223523.20130-1-rdunlap@infradead.org>
Fix a typo (supportinf -> supporting).
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>
Cc: linux-doc@vger.kernel.org
---
Documentation/input/uinput.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20210202.orig/Documentation/input/uinput.rst
+++ linux-next-20210202/Documentation/input/uinput.rst
@@ -179,7 +179,7 @@ uinput old interface
--------------------
Before uinput version 5, there wasn't a dedicated ioctl to set up a virtual
-device. Programs supportinf older versions of uinput interface need to fill
+device. Programs supporting older versions of uinput interface need to fill
a uinput_user_dev structure and write it to the uinput file descriptor to
configure the new uinput device. New code should not use the old interface
but interact with uinput via ioctl calls, or use libevdev.
next prev parent reply other threads:[~2021-03-02 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 22:35 [PATCH 0/8] input: Documentation: corrections to Doc/input/ files Randy Dunlap
2021-03-02 22:35 ` [PATCH 1/8] input: Documentation: corrections for input.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 2/8] input: Documentation: corrections for event-codes.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 3/8 RESEND] input: Documentation: update related file names in ff.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 4/8] input: Documentation: corrections for gameport-programming.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 5/8] input: Documentation: corrections for multi-touch-protocol.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 6/8] input: Documentation: corrections for notifier.rst Randy Dunlap
2021-03-02 22:35 ` [PATCH 7/8] input: Documentation: corrections for input-programming.rst Randy Dunlap
2021-03-02 22:35 ` Randy Dunlap [this message]
2021-03-09 0:16 ` [PATCH 0/8] input: Documentation: corrections to Doc/input/ files Jonathan Corbet
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=20210302223523.20130-9-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.