From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] doc: fix typos in virtualization gsg
Date: Mon, 7 Jan 2019 08:49:55 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9FE00C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20181229115009.5785-1-ramirose@gmail.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Saturday, December 29, 2018 7:50 PM
> To: dts@dpdk.org
> Cc: Rami Rosen <ramirose@gmail.com>
> Subject: [dts] [PATCH] doc: fix typos in virtualization gsg
>
> This patch fixes 3 typos in virtualization gsg
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> doc/dts_gsg/virtualization.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/dts_gsg/virtualization.rst b/doc/dts_gsg/virtualization.rst
> index d9b409d..df6b681 100755
> --- a/doc/dts_gsg/virtualization.rst
> +++ b/doc/dts_gsg/virtualization.rst
> @@ -247,7 +247,7 @@ Before VM operations, vxlan sample feature request
> to start tep_termination appl .. code-block:: console
>
> def prepare_vxlan_sample_env(self, tep_cmd):
> - # remove unexpected socke
> + # remove unexpected socket
> self.dut.send_expect("rm -rf vhost-net", "# ")
>
> # start tep_termination first
> @@ -479,10 +479,10 @@ Options for nic:
> +-----------------+----------------------------------+----------------+-----------+
> | opt_vlan | vlan of virtual nic | 0
> | No |
> +-----------------+----------------------------------+----------------+-----------+
> - | opt_macaddr | If not assgin, nic will generate | N/A
> | No |
> + | opt_macaddr | If not assign, nic will generate | N/A
> | No |
> | | random mac |
> | |
> +-----------------+----------------------------------+----------------+-----------+
> - | opt_model | model of virutal nic | e1000
> | No |
> + | opt_model | model of virtual nic | e1000
> | No |
> +-----------------+----------------------------------+----------------+-----------+
> | opt_name | name be assigned for use in | N/A
> | No |
> | | monitor command |
> | |
> --
> 2.19.2
prev parent reply other threads:[~2019-01-07 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 11:50 Rami Rosen
2019-01-07 8:49 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0B9FE00C@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ramirose@gmail.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).