From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>, john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: enic SR-IOV configurations
Date: Wed, 26 Apr 2017 10:31:08 +0100 [thread overview]
Message-ID: <fe45d31c-af42-bf83-7e09-32cd95f87bff@intel.com> (raw)
In-Reply-To: <20170426055619.16452-1-johndale@cisco.com>
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.
Also enic feature table (enic.ini) is not announcing SR-IOV support, can
you please fix it?
Thanks,
ferruh
[1]
doc/guides/nics/enic.rst:181: WARNING: Could not lex literal_block as
"c". Highlighting skipped.
next prev parent reply other threads:[~2017-04-26 9:31 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 [this message]
2017-04-26 14:55 ` Mcnamara, John
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=fe45d31c-af42-bf83-7e09-32cd95f87bff@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.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).