dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	 "Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix PDF build of bbdev prog guide
Date: Thu, 18 Jul 2019 14:51:15 +0000	[thread overview]
Message-ID: <1183128033837D43A851F70F33ED5C575C1FD4F3@FMSMSX109.amr.corp.intel.com> (raw)
In-Reply-To: <2158485.gHaOC2YqBv@xps>

From: Thomas Monjalon [mailto:thomas@monjalon.net] 
>18/07/2019 08:24, Nicolas Chautru:
>> Some machine (like on dpdk.org) may fail to build the prog guide PDF because of the complex table inserted in the bbdev chapter.
>> 
>> Fixes: 3f3f608142cf ("doc: update bbdev guide for 5GNR operations")
>> 
>> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
>
>Thanks for the quick reaction.
>If you agree, I can apply this patch without the changes of figure refs.

No problem, we can fix the other cosmetic changes that you have raised post 19.09. 

>About the tables, there are simpler syntax in RsT:
>http://docutils.sourceforge.net/docs/user/rst/quickref.html#tables

To be honest, I cannot see the problem with the current format which is following that structure already. 
What error message do you get on your machine? This is not caught on DPDK CI, is it? 

>You can also consider the definition lists:
>http://docutils.sourceforge.net/docs/user/rst/quickref.html#definition-lists

Clearer has a formal table from my point of view. 

Thanks


  reply	other threads:[~2019-07-18 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18  6:24 [dpdk-dev] [PATCH] doc: fix PDF build of bbdev prog guide Nicolas Chautru
2019-07-18 13:53 ` Thomas Monjalon
2019-07-18 14:43   ` Chautru, Nicolas
2019-07-18 15:01     ` Thomas Monjalon
2019-07-18 15:09       ` Chautru, Nicolas
2019-07-18 13:57 ` Thomas Monjalon
2019-07-18 14:51   ` Chautru, Nicolas [this message]
2019-07-18 15:05     ` Thomas Monjalon
2019-07-18 21:49 ` Thomas Monjalon
2019-07-18 22:01 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2019-07-18 22:04   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2019-07-17 22:01 [dpdk-dev] [PATCH] " Thomas Monjalon
2019-07-18 13:33 ` Chautru, Nicolas
2019-07-18 13:47   ` Thomas Monjalon
2019-07-18 14:59     ` Chautru, Nicolas
2019-07-18 15:09       ` 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=1183128033837D43A851F70F33ED5C575C1FD4F3@FMSMSX109.amr.corp.intel.com \
    --to=nicolas.chautru@intel.com \
    --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).