From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: fix unreadable images
Date: Tue, 14 Feb 2017 13:14:47 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026CBF06@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1487073334-72469-1-git-send-email-harry.van.haaren@intel.com>
> -----Original Message-----
> From: Van Haaren, Harry
> Sent: Tuesday, February 14, 2017 11:56 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: thomas.monjalon@6wind.com; dev@dpdk.org; Tan, Jianfeng
> <jianfeng.tan@intel.com>; Van Haaren, Harry <harry.van.haaren@intel.com>
> Subject: [PATCH v3] doc: fix unreadable images
>
> From: Jianfeng Tan <jianfeng.tan@intel.com>
>
> The images by below two commits are very unclear. Fix it.
>
> Fixes: 50665deebda ("doc: add guide to use virtio-user for container
> networking")
> Fixes: 0ba3870e755 ("doc: add guide to use virtio-user as exceptional
> path")
>
> Suggested-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-02-14 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 11:18 [dpdk-dev] [PATCH] " Jianfeng Tan
2017-02-10 13:10 ` Thomas Monjalon
2017-02-13 7:45 ` [dpdk-dev] [PATCH v2] " Jianfeng Tan
2017-02-13 9:45 ` Thomas Monjalon
2017-02-14 10:46 ` Thomas Monjalon
2017-02-14 11:48 ` Mcnamara, John
2017-02-14 11:55 ` [dpdk-dev] [PATCH v3] " Harry van Haaren
2017-02-14 13:14 ` Mcnamara, John [this message]
2017-02-14 14:25 ` 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=B27915DBBA3421428155699D51E4CFE2026CBF06@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=thomas.monjalon@6wind.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).