From: Yasufumi Ogawa <yasufum.o@gmail.com>
To: Itsuro ODA <oda@valinux.co.jp>
Cc: spp@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [spp] [PATCH v3 0/3] add vdev_test
Date: Fri, 13 Mar 2020 09:44:34 +0900 [thread overview]
Message-ID: <f80facab-2fae-d6ed-eb27-b07a45788383@gmail.com> (raw)
In-Reply-To: <20200311102559.E201.277DD91C@valinux.co.jp>
> Hi Yasufumi,
>
>>> vdev_test is a simple tool to perform packet forwarding for
>>> virtual ethernet devices. It is mainly to test pipe PMD
>>> because testpmd can not be secondary process but vdev_test
>>> can be.
>> Applied, thanks.
>
> I received "Applied" on 5th March but git has not been
> update yet. When is it going to update ?
I'll merge all patches in waiting list after HIdeyuki's update.
Thanks
>
> Thanks.
>
prev parent reply other threads:[~2020-03-13 0:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 2:02 [spp] [PATCH 0/2] " Itsuro Oda
2020-02-26 2:02 ` [spp] [PATCH 1/2] vdev_test: simple tool to perform packet forwarding for vdev Itsuro Oda
2020-02-26 2:02 ` [spp] [PATCH 2/2] makefile: add to build vdev_test Itsuro Oda
2020-02-27 4:25 ` [spp] [PATCH v2 0/3] add vdev_test Itsuro Oda
2020-02-27 4:25 ` [spp] [PATCH v2 1/3] vdev_test: simple tool to perform packet forwarding for vdev Itsuro Oda
2020-02-28 8:32 ` Yasufumi Ogawa
2020-02-27 4:25 ` [spp] [PATCH v2 2/3] tools: add Makefile for vdev_test Itsuro Oda
2020-02-27 4:25 ` [spp] [PATCH v2 3/3] makefile: add make of tools directory Itsuro Oda
2020-03-02 0:00 ` [spp] [PATCH v3 0/3] add vdev_test Itsuro Oda
2020-03-02 0:00 ` [spp] [PATCH v3 1/3] vdev_test: simple tool to perform packet forwarding for vdev Itsuro Oda
2020-03-02 0:00 ` [spp] [PATCH v3 2/3] tools: add Makefile for vdev_test Itsuro Oda
2020-03-02 0:00 ` [spp] [PATCH v3 3/3] makefile: add make of tools directory Itsuro Oda
2020-03-05 1:25 ` [spp] [PATCH v3 0/3] add vdev_test Yasufumi Ogawa
2020-03-11 1:25 ` Itsuro ODA
2020-03-13 0:44 ` Yasufumi Ogawa [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=f80facab-2fae-d6ed-eb27-b07a45788383@gmail.com \
--to=yasufum.o@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=oda@valinux.co.jp \
--cc=spp@dpdk.org \
/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).