From: Dan Gora <dg@adax.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
dev@dpdk.org, Natalie Samsonov <nsamsono@marvell.com>
Subject: Re: [dpdk-dev] PDF guides broken
Date: Mon, 29 Oct 2018 17:22:57 -0300 [thread overview]
Message-ID: <CAGyogRYMwrAabC9_mutyQdS-ZOkJ8fcaM6P-XXnqf9ixNRxOfA@mail.gmail.com> (raw)
In-Reply-To: <1683636.1WRA8gqML0@xps>
It looks like it's choking on a figure in the mvpp2.rst file:
guides/nics/mvpp2.rst:.. figure:: img/mvpp2_tm.svg
Reverting commit 0ba610ca1d178cbeedba6e033ee399dfe773801e fixes it.
This fixes it too:
diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst
index 59fa0e10d..10303a1c1 100644
--- a/doc/guides/nics/mvpp2.rst
+++ b/doc/guides/nics/mvpp2.rst
@@ -644,7 +644,7 @@ Node which has a parent is called a leaf whereas
node without
parent is called a non-leaf (root).
MVPP2 PMD supports two level hierarchy where level 0 represents ports
and level 1 represents tx queues of a given port.
-.. figure:: img/mvpp2_tm.svg
+.. figure:: img/mvpp2_tm.*
On Mon, Oct 29, 2018 at 12:38 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> Hi,
>
> The command make-guides-pdf fails currently (18.11-rc1).
> There is probably a subtle syntax error in one of the RST file.
>
> Please, who wants to look at the issue and fix it?
>
> Thank you
>
>
next prev parent reply other threads:[~2018-10-29 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 3:37 Thomas Monjalon
2018-10-29 20:22 ` Dan Gora [this message]
2018-10-30 9:07 ` Kovacevic, Marko
2018-10-30 9:42 ` Thomas Monjalon
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=CAGyogRYMwrAabC9_mutyQdS-ZOkJ8fcaM6P-XXnqf9ixNRxOfA@mail.gmail.com \
--to=dg@adax.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nsamsono@marvell.com \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).