public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, dmitry.torokhov@gmail.com,
	linux-input@vger.kernel.org, benjamin.tissoires@redhat.com
Subject: Re: [PATCH v2] Docs: Input: initial uinput documentation
Date: Mon, 27 Mar 2017 09:08:50 +1000	[thread overview]
Message-ID: <20170326230850.GB14405@jelly> (raw)
In-Reply-To: <20170326164106.GB2267@xfiles.domain.name>

On Sun, Mar 26, 2017 at 01:41:08PM -0300, Marcos Paulo de Souza wrote:
> Hi Jon,
> 
> On Fri, Mar 24, 2017 at 03:17:03PM -0600, Jonathan Corbet wrote:
> > On Fri, 24 Mar 2017 00:34:58 -0300
> > Marcos Paulo de Souza <marcos.souza.org@gmail.com> wrote:
> > 
> > > this is the second iteration of this patch. The first version can be checked
> > > here[1]. A special thanks to Peter Hutterer who dug the last patch and suggested
> > > a lot of changes , hopefully, all addressed in this version.
> > 
> > This seems like a good start.  Of course, I have a couple of comments...
> > 
> > 1) RST documentation is good, but it really needs to be hooked into the
> >    docs build with the rest.  In this case, it needs to go into the
> >    application developer's manual.  The only slight snag is ... well ...
> >    that manual doesn't quite exist yet.  Once this is ready, if it comes
> >    through me tree, I can follow it with a patch creating that manual and
> >    moving this section into it.
> 
> Sounds good. If you want, I can verify and add this new page as well.
> 
> > 
> > 2) We don't normally put in section numbers manually in RST documents,
> >    since Sphinx will do that for us.
> 
> Great, fixed here.
> 
> > 
> > 3) Section 3.0 covers the old interface.  I'm not sure we need that in 
> >    documentation in current kernels which, by definition, have the
> >    current interface.
> 
> Currently both interces can be used in mainline, but this can be nice to have for users
> who still run older kernels. But I can remove if you strongly disagree.

Given the kernel's policy for retiring interfaces, the old interface will be
available forever. But at this point you shouldn't be writing new software
against the old interface.

Cheers,
   Peter

      reply	other threads:[~2017-03-26 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  3:34 [PATCH v2] Docs: Input: initial uinput documentation Marcos Paulo de Souza
2017-03-24  3:34 ` [PATCH v2] Documentation: Input: Add " Marcos Paulo de Souza
2017-03-24  4:39   ` Peter Hutterer
2017-03-26 16:21     ` Marcos Paulo de Souza
2017-03-26 22:52       ` Peter Hutterer
2017-03-27  2:23         ` Marcos Paulo de Souza
2017-03-24 21:17 ` [PATCH v2] Docs: Input: initial " Jonathan Corbet
2017-03-26 16:41   ` Marcos Paulo de Souza
2017-03-26 23:08     ` Peter Hutterer [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=20170326230850.GB14405@jelly \
    --to=peter.hutterer@who-t.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=marcos.souza.org@gmail.com \
    /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