mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Subject: [PATCH] Docs: Input: initial uinput documentation
Date: Wed, 22 Mar 2017 00:01:56 -0300	[thread overview]
Message-ID: <20170322030201.4423-1-marcos.souza.org@gmail.com> (raw)
In-Reply-To: <20170322025820.4108-2-marcos.souza.org@gmail.com>

Hi guys,

so, after taking some time to understand how to work with uinput, and to grab some examples
on web, I discovered that kernel doesn't have any "official" documentation about it.

So, here we are :)

I added some examples based in my tests, there are samples of EV_REL and EV_KEY, but
we can add more in the future to cover other cases.

Notes:
* I created the doc in rst format, following the trend to adapt all documentation using the
  new format (although input subsystem still have some work to do...)
* This documentation was converted to HTML, and it can be checked here:
  https://marcosps.github.io/
* Let me know if you find anything that can make the documentation more clear, or
  anything that can make the code better

Marcos Paulo de Souza (1):
  Documentation: Input: Add uinput documentation

 Documentation/input/uinput.rst | 158 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 158 insertions(+)
 create mode 100644 Documentation/input/uinput.rst

-- 
2.9.3

  reply	other threads:[~2017-03-22  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170322025820.4108-1-marcos.souza.org@gmail.com>
2017-03-22  2:58 ` [PATCH] Documentation: Input: Add " Marcos Paulo de Souza
2017-03-22  3:01   ` Marcos Paulo de Souza [this message]
2017-03-22  4:03   ` Peter Hutterer
2017-03-23  2:54     ` Marcos Paulo de Souza
2017-03-23  3:23       ` Peter Hutterer
2017-03-21 15:28         ` Marcos Paulo de Souza

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=20170322030201.4423-1-marcos.souza.org@gmail.com \
    --to=marcos.souza.org@gmail.com \
    --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

all inboxes | Powered by JetHome®