From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-input@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH 7/8] Input: docs - split input docs into kernel- and user-facing
Date: Sun, 16 Apr 2017 11:50:57 -0300 [thread overview]
Message-ID: <20170416115053.233b5a37@vento.lan> (raw)
In-Reply-To: <20170416110813.66a4ba64@vento.lan>
Em Sun, 16 Apr 2017 11:08:13 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> Hi Dmitry,
>
> Em Sat, 15 Apr 2017 22:11:44 -0700
> Dmitry Torokhov <dmitry.torokhov@gmail.com> escreveu:
>
> > Split input documentation into several groups: kernel- and user-facing, and
> > notes about individual device drivers. Move device drivers docs into a
> > separate subdirectory.
>
> I reviewed and tested Sphinx generation for this patch series.
> Thinks are a way better organized now. Good work!
>
> I got just a minor nitpick for HTML generation (see below).
>
>
> However, building PDF documentation now hits an error, with Sphinx 1.4.9:
>
> Markup is unsupported in LaTeX:
> input/devices/xpad:209: literal blocks in footnotes are not supported by LaTeX
>
> It seems it didn't like to have literal blocks inside footnotes:
>
> .. [4] /proc/bus/usb/devices - dump from InterAct PowerPad Pro (Germany):
>
> ::
>
> T: Bus=01 Lev=03 Prnt=04 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs= 1
> P: Vendor=05fd ProdID=107a Rev= 1.00
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=58(unk. ) Sub=42 Prot=00 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl= 10ms
> E: Ad=02(O) Atr=03(Int.) MxPS= 32 Ivl= 10ms
>
>
> I'll see if I can find a way to fix this issue.
The enclosed patch should fix it. It should come after the one that
replaces /proc/bus/usb/devices to /sys/kernel/debug/usb/devices.
It also fixes the last reference to the last URL.
Thanks,
Mauro
next prev parent reply other threads:[~2017-04-16 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 5:11 [PATCH 1/8] Input: move documentation for Amiga CD32 Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 2/8] Input: rotary-encoder - remove references to platform data from docs Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 3/8] Input: fix "Game console" heading level in joystick documentation Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 4/8] Input: docs - remove disclaimer/GPL notice Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 5/8] Input: docs - update joystick documentation a bit Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 6/8] Input: docs - note that MT-A protocol is obsolete Dmitry Torokhov
2017-04-16 5:11 ` [PATCH 7/8] Input: docs - split input docs into kernel- and user-facing Dmitry Torokhov
2017-04-16 14:08 ` Mauro Carvalho Chehab
2017-04-16 14:50 ` Mauro Carvalho Chehab [this message]
2017-04-16 5:11 ` [PATCH 8/8] Input: docs - freshen up introduction Dmitry Torokhov
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=20170416115053.233b5a37@vento.lan \
--to=mchehab@s-opensource.com \
--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 \
--cc=mchehab@kernel.org \
--cc=vojtech@suse.cz \
/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