From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Yong Wang <wang.yong19@zte.com.cn>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc/failsafe: fix typos in nics guide
Date: Fri, 18 Aug 2017 13:23:35 +0200 [thread overview]
Message-ID: <20170818112334.GU8124@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1503053868-31177-1-git-send-email-wang.yong19@zte.com.cn>
On Fri, Aug 18, 2017 at 06:57:48AM -0400, Yong Wang wrote:
> Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
> doc/guides/nics/fail_safe.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst
> index 34ecae2..c4e3d2e 100644
> --- a/doc/guides/nics/fail_safe.rst
> +++ b/doc/guides/nics/fail_safe.rst
> @@ -136,7 +136,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD.
> .. code-block:: console
>
> $RTE_TARGET/build/app/testpmd -c 0xff -n 4 \
> - --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)'
> + --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \
> -b 84:00.0 -b 00:04.0 -- -i
>
> If the slave device being used is not blacklisted, it will be probed by the
> @@ -150,7 +150,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD.
> .. code-block:: console
>
> $RTE_TARGET/build/app/testpmd -c 0xff -n 4 \
> - --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)'
> + --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \
> -w 81:00.0 -- -i
>
> #. Start testpmd using a flexible device definition
> --
> 1.8.3.1
>
>
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2017-08-18 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:57 Yong Wang
2017-08-18 11:23 ` Gaëtan Rivet [this message]
2017-08-21 11:27 ` 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=20170818112334.GU8124@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=wang.yong19@zte.com.cn \
/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).