From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] doc: fix unreadable images
Date: Tue, 14 Feb 2017 15:25:04 +0100 [thread overview]
Message-ID: <5244837.NjQ6dHlZHs@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026CBF06@IRSMSX103.ger.corp.intel.com>
2017-02-14 13:14, Mcnamara, John:
> > -----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>
Applied, thanks
prev parent reply other threads:[~2017-02-14 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 11:18 [PATCH] doc: fix unreadable images Jianfeng Tan
2017-02-10 13:10 ` Thomas Monjalon
2017-02-13 7:45 ` [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 ` [PATCH v3] " Harry van Haaren
2017-02-14 13:14 ` Mcnamara, John
2017-02-14 14:25 ` Thomas Monjalon [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=5244837.NjQ6dHlZHs@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=john.mcnamara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.