From: Stephen Hemminger <stephen@networkplumber.org>
To: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: [dpdk-dev] make doc fails
Date: Fri, 21 Jun 2019 12:56:28 -0700 [thread overview]
Message-ID: <20190621125628.53222940@hermes.lan> (raw)
Just tried make doc on current DPDK tree and it fails:
/home/shemminger/git/dpdk/doc/guides/faq/faq.rst:7: WARNING: undefined label: linux_gsg (if the link has no caption the label must precede a section header)
/home/shemminger/git/dpdk/doc/guides/faq/faq.rst:25: WARNING: undefined label: linux_gsg (if the link has no caption the label must precede a section header)
/home/shemminger/git/dpdk/doc/guides/faq/faq.rst:190: WARNING: undefined label: multi_process_app (if the link has no caption the label must precede a section header)
Not sure what the bad commit is. Also, not sure why CI didn't catch it.
next reply other threads:[~2019-06-21 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 19:56 Stephen Hemminger [this message]
2019-06-23 22:46 ` Thomas Monjalon
2019-06-24 14:53 ` Ferruh Yigit
2019-06-24 15:04 ` Burakov, Anatoly
2019-06-24 15:27 ` Stephen Hemminger
2019-06-24 16:09 ` Morten Brørup
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=20190621125628.53222940@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).