From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix sphinx warning
Date: Wed, 19 Apr 2017 14:16:19 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612A2EA5D@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20170419121036.4408-1-thomas@monjalon.net>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, April 19, 2017 1:11 PM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: fix sphinx warning
>
> Seen with recent version of sphinx:
> WARNING: latex_preamble conflicts with latex_elements['preamble'], ignored.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Previously I had this warning, but no more, whooo!
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
prev parent reply other threads:[~2017-04-19 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 12:10 Thomas Monjalon
2017-04-19 12:21 ` Ferruh Yigit
2017-04-19 13:25 ` Thomas Monjalon
2017-04-19 14:16 ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA612A2EA5D@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).