From: Akira Yokosawa <akiyks@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-serial@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 0/3] Documentation: Fix issues with Oxford Semiconductor PCIe (Tornado) 950
Date: Sun, 15 May 2022 18:11:47 +0900 [thread overview]
Message-ID: <f4d40da6-756b-9e75-b867-cc9eedc4b232@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2205131712410.10656@angie.orcam.me.uk>
Hi Maciej,
On Fri, 13 May 2022 23:41:57 +0100 (BST),
Maciej W. Rozycki wrote:
> Hi,
>
[...]
>
> For the latter command however I need to note that several other
> documents in our Documentation/ tree suffer from a problem that causes
> `make pdfdocs' to fail (and the failure cannot be worked around with
> make's `-k -i' options, i.e. no output is ever produced), e.g.:
>
> Markup is unsupported in LaTeX:
> filesystems/9p:: nested tables are not yet implemented.
>
> and similarly for: filesystems/erofs, filesystems/f2fs, filesystems/ntfs,
> networking/device_drivers/ethernet/dlink/dl2k, scsi/arcmsr_spec,
> scsi/g_NCR5380, scsi/ncr53c8xx, and scsi/sym53c8xx_2. I don't know if it
> is a known problem, possibly addressed in a newer version of tools, so
> I've thought it might be worth reporting.
>
[...]
>
> NB XeTeX, Version 3.14159265-2.6-0.99999 (TeX Live 2019/dev/Debian) and
> Sphinx 1.8.4 here.
As mentioned in the section titled "PDF and LaTeX builds" in
Documentation/doc-guide/sphinx.rst, "make pdfdocs" requires Sphinx 2.4 or
later.
Another hint for you.
You can say "make SPHINXDIRS=<sub dir> htmldocs pdfdocs" to
test-build docs under Documentation/<sub dir>/.
You might see false warnings of "WARNING: undefined label: ..."
which you wouldn't see in full builds, though.
Hope this helps.
I see there is no mention of the SPHINXDIRS make variable in the
doc-guide. I'll see it can be explained somewhere in sphinx.rst.
Thanks, Akira
>
> The issues are not directly related to the changes proposed here though,
> so please apply them.
>
> Maciej
next prev parent reply other threads:[~2022-05-15 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 22:41 [PATCH 0/3] Documentation: Fix issues with Oxford Semiconductor PCIe (Tornado) 950 Maciej W. Rozycki
2022-05-13 22:42 ` [PATCH 1/3] Documentation: Move Oxford Semiconductor PCIe (Tornado) 950 to misc-devices Maciej W. Rozycki
2022-05-13 22:42 ` [PATCH 2/3] Documentation: Reformat Oxford Semiconductor PCIe (Tornado) 950 Maciej W. Rozycki
2022-05-13 22:42 ` [PATCH 3/3] Documentation: Wire " Maciej W. Rozycki
2022-05-14 5:50 ` Bagas Sanjaya
2022-05-14 5:51 ` Bagas Sanjaya
2022-05-14 13:58 ` Maciej W. Rozycki
2022-05-15 9:11 ` Akira Yokosawa [this message]
2022-05-15 11:02 ` [PATCH 0/3] Documentation: Fix issues with " Maciej W. Rozycki
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=f4d40da6-756b-9e75-b867-cc9eedc4b232@gmail.com \
--to=akiyks@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=sfr@canb.auug.org.au \
/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