linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/8] input: Documentation: corrections to Doc/input/ files
Date: Tue,  2 Mar 2021 14:35:15 -0800	[thread overview]
Message-ID: <20210302223523.20130-1-rdunlap@infradead.org> (raw)

Update several Documentation/input/ files for wording, punctutation,
struct info, and file names.

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

 [PATCH 1/8] input: Documentation: corrections for input.rst
 [PATCH 2/8] input: Documentation: corrections for event-codes.rst
 [PATCH 3/8 RESEND] input: Documentation: update related file names in ff.rst
 [PATCH 4/8] input: Documentation: corrections for gameport-programming.rst
 [PATCH 5/8] input: Documentation: corrections for multi-touch-protocol.rst
 [PATCH 6/8] input: Documentation: corrections for notifier.rst
 [PATCH 7/8] input: Documentation: corrections for input-programming.rst
 [PATCH 8/8] input: Documentation: corrections for uinput.rst

 Documentation/input/event-codes.rst          |   10 ++--
 Documentation/input/ff.rst                   |    6 +-
 Documentation/input/gameport-programming.rst |   35 +++++++++++------
 Documentation/input/input-programming.rst    |   20 ++++-----
 Documentation/input/input.rst                |    8 +--
 Documentation/input/multi-touch-protocol.rst |    8 +--
 Documentation/input/notifier.rst             |    3 -
 Documentation/input/uinput.rst               |    2 
 8 files changed, 52 insertions(+), 40 deletions(-)

             reply	other threads:[~2021-03-03  5:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 22:35 Randy Dunlap [this message]
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 ` [PATCH 8/8] input: Documentation: corrections for uinput.rst Randy Dunlap
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-1-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 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).