DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	john.mcnamara@intel.com, amr.mokhtar@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: fix bbdev test guide build
Date: Thu, 25 Jan 2018 18:45:39 +0100	[thread overview]
Message-ID: <17862807.EDDqhdpkuX@xps> (raw)
In-Reply-To: <20180125164820.GA10052@bricha3-MOBL3.ger.corp.intel.com>

25/01/2018 17:48, Bruce Richardson:
> On Wed, Jan 24, 2018 at 03:07:45PM +0000, Marko Kovacevic wrote:
> > Fix build issue with pdf guides. Some indentations in the bbdev test
> > application doc were causing build failures. Latex Log message:
> >  
> >     doc.log:! LaTeX Error: Too deeply nested.
> >    
> > Fixes: f714a18885a6 ("app/testbbdev: add test application for bbdev")
> > Cc: amr.mokhtar@intel.com
> >  
> > 
> > Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
> > ---
> > 
> > V2: Added more information into commit message
> >     about the issue
> 
> [Please use --in-reply-to to chain emails into a thread when sending v2's
> and v3's etc. of patches.]
> 
> This fixes the errors I see with "make doc-guides-pdf" and the pdf
> output looks ok for that section too.
> 
> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks

      reply	other threads:[~2018-01-25 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 15:07 Marko Kovacevic
2018-01-25 16:48 ` Bruce Richardson
2018-01-25 17:45   ` Thomas Monjalon [this message]

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=17862807.EDDqhdpkuX@xps \
    --to=thomas@monjalon.net \
    --cc=amr.mokhtar@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    /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).