From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] doc: update the vhost sample guide
Date: Fri, 4 Nov 2016 13:38:26 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20264A8DE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1478056501-9321-3-git-send-email-yuanhan.liu@linux.intel.com>
> -----Original Message-----
> From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> Sent: Wednesday, November 2, 2016 3:15 AM
> To: dev@dpdk.org
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Yuanhan Liu
> <yuanhan.liu@linux.intel.com>
> Subject: [PATCH 2/3] doc: update the vhost sample guide
>
> For vhost-switch sample, the old guide takes too many words on
> vhost-cuse, which is mainly due to vhost-cuse is invented before
> vhost-user.
>
> Now vhost-cuse is removed, meaning the best part of the doc is useless.
> Instead of amending one piece here and there, this patch simply removes
> the most part of the doc and replace it with a simple test guide.
>
> For tep_term sample, mainly for removing the part has "vhost-cuse".
>
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Good cleanup.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2016-11-04 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 3:14 [dpdk-dev] [PATCH 0/3] vhost: comments and doc update due to vhost-cuse removal Yuanhan Liu
2016-11-02 3:14 ` [dpdk-dev] [PATCH 1/3] doc: update vhost programming guide Yuanhan Liu
2016-11-04 13:22 ` Mcnamara, John
2016-11-02 3:15 ` [dpdk-dev] [PATCH 2/3] doc: update the vhost sample guide Yuanhan Liu
2016-11-04 13:38 ` Mcnamara, John [this message]
2016-11-02 3:15 ` [dpdk-dev] [PATCH 3/3] vhost: update comments Yuanhan Liu
2016-11-04 13:28 ` Mcnamara, John
2016-11-04 14:15 ` Yuanhan Liu
2016-11-07 15:00 ` [dpdk-dev] [PATCH 0/3] vhost: comments and doc update due to vhost-cuse removal Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE20264A8DE@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.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).