From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>,
"Liu, Yong" <yong.liu@intel.com>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, John Daley <johndale@cisco.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: enic SR-IOV configurations
Date: Wed, 26 Apr 2017 14:55:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2332C2941@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <fe45d31c-af42-bf83-7e09-32cd95f87bff@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Wednesday, April 26, 2017 10:31 AM
> To: John Daley <johndale@cisco.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: enic SR-IOV configurations
>
> On 4/26/2017 6:56 AM, John Daley wrote:
> > Document SR-IOV passthrough setup and limitations for enic PMD.
> >
> > Signed-off-by: John Daley <johndale@cisco.com>
>
> Hi John,
>
> Thank you for the documentation update, just I am getting following
> warning [1], can you please check.
>
> ...
> doc/guides/nics/enic.rst:181: WARNING: Could not lex literal_block as "c".
> Highlighting skipped.
Hi,
To catch issues like this could we add a "make doc" test to the automated patch tests.
Thanks,
John
next prev parent reply other threads:[~2017-04-26 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 5:56 John Daley
2017-04-26 9:31 ` Ferruh Yigit
2017-04-26 14:55 ` Mcnamara, John [this message]
2017-04-26 14:49 ` Mcnamara, John
2017-04-27 0:52 ` [dpdk-dev] [PATCH v2] " John Daley
2017-04-27 10:12 ` Mcnamara, John
2017-04-27 10:51 ` Ferruh Yigit
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=B27915DBBA3421428155699D51E4CFE2332C2941@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=qian.q.xu@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=yong.liu@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).