From: Ferruh Yigit <ferruh.yigit@intel.com>
To: x-fn-spp@sl.ntt-tx.co.jp, ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: Re: [spp] [PATCH v3 0/3] docs:improvement of document under VF directory
Date: Wed, 15 Aug 2018 16:28:43 +0100 [thread overview]
Message-ID: <04762961-e123-dd25-1b4e-4a2f7a7babba@intel.com> (raw)
In-Reply-To: <201806150751.w5F7prZX017959@imss03.silk.ntt-tx.co.jp>
On 6/15/2018 8:51 AM, x-fn-spp@sl.ntt-tx.co.jp wrote:
> From: Hiroyuki Nakamura <nakamura.hiroyuki@po.ntt-tx.co.jp>
>
> Yasufumi-san, thanks for your comments again.
> Following your comments, I revised 2nd patch.
> About 1st and 3rd patch, content is the same with that of version2.
>
> Change on 2nd patch:
> Remove $SPP_HOME because it is not necessary environment
> variable.
>
> BR,
> Hiroyuki
>
> Hiroyuki Nakamura (3):
> docs: add how to install qemu 2.7
> docs: correct incorrect SPP git URL
> docs: delete unsupported SPP VF Secondary Command
Series applied, thanks.
next prev parent reply other threads:[~2018-08-15 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 9:01 [spp] [PATCH " x-fn-spp
2018-06-13 8:48 ` [spp] [PATCH v2 " x-fn-spp
2018-06-15 7:51 ` [spp] [PATCH v3 " x-fn-spp
2018-08-15 15:28 ` Ferruh Yigit [this message]
2018-06-15 7:51 ` [spp] [PATCH v3 1/3] docs: add how to install qemu 2.7 x-fn-spp
2018-06-15 8:33 ` Yasufumi Ogawa
2018-06-15 7:51 ` [spp] [PATCH v3 2/3] docs: correct incorrect SPP git URL x-fn-spp
2018-06-15 8:34 ` Yasufumi Ogawa
2018-06-15 7:51 ` [spp] [PATCH v3 3/3] docs: delete unsupported SPP VF Secondary Command x-fn-spp
2018-06-15 8:34 ` Yasufumi Ogawa
2018-06-13 8:48 ` [spp] [PATCH v2 1/3] docs: add how to install qemu 2.7 x-fn-spp
2018-06-15 2:34 ` Yasufumi Ogawa
2018-08-15 15:24 ` Ferruh Yigit
2018-08-15 15:28 ` Ferruh Yigit
2018-06-13 8:48 ` [spp] [PATCH v2 2/3] docs: correct incorrect SPP git URL x-fn-spp
2018-06-13 8:48 ` [spp] [PATCH v2 3/3] docs: delete unsupported SPP VF Secondary Command x-fn-spp
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=04762961-e123-dd25-1b4e-4a2f7a7babba@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.org \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).