From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Martin Kepplinger <martink@posteo.de>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] docs-rst: add input docs at main index and use kernel-figure
Date: Tue, 11 Apr 2017 14:54:16 -0600 [thread overview]
Message-ID: <20170411145416.2cf4d180@lwn.net> (raw)
In-Reply-To: <1183dff3e0dd809c866d646a0c41ddbc4452d85e.1491904368.git.mchehab@s-opensource.com>
On Tue, 11 Apr 2017 07:01:19 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> This patch contains the final bits of the input documentation
> conversion. The linux-input tree has already the ReST conversion
> patches, but it doesn't have the
> Documentation/sphinx/load_config.py script with implements
> the kernel-figure directive, as it got merged via docs tree.
>
> So, either one of you should merge from the other tree or this
> patch should be sent in separate upstream after both trees
> gets merged. What do you prefer?
How about if I send it Linusward toward the end of the merge window?
FWIW, while I think the conversion is great, I'm not fully pleased with
having it as a separate top-level document. Probably what needs to be
done here is to split it up into two pieces, one for driver-api and one
for userspace-api. But that can happen later, I guess.
Thanks,
jon
next prev parent reply other threads:[~2017-04-11 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 10:01 [PATCH] docs-rst: add input docs at main index and use kernel-figure Mauro Carvalho Chehab
2017-04-11 20:54 ` Jonathan Corbet [this message]
2017-04-12 9:49 ` Mauro Carvalho Chehab
2017-05-09 19:41 ` Jonathan Corbet
2017-05-11 10:44 ` Mauro Carvalho Chehab
2017-05-11 17:50 ` 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=20170411145416.2cf4d180@lwn.net \
--to=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.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 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.