From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH 0/2] Fix bug for patch not found error
Date: Thu, 24 May 2018 13:56:30 +0100 [thread overview]
Message-ID: <024f61be-c1fa-56f4-6602-fc331cb5402a@intel.com> (raw)
In-Reply-To: <20180515012049.8785-1-ogawa.yasufumi@lab.ntt.co.jp>
On 5/15/2018 2:20 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Hi,
>
> This patch is for fixing a bug of patch command. In SPP controller, it
> is failed to patch to pcap or nullpmd for not found error. To fix the
> bug, add pcap and nullpmd to definition of port types.
>
> Thanks,
> Yasufumi
>
>
> Yasufumi Ogawa (2):
> spp_nfv: fix bug for patching PMDs
> controller: fix bug for patching PMDs
Series applied, thanks.
prev parent reply other threads:[~2018-05-24 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:20 ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 1/2] spp_nfv: fix bug for patching PMDs ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 2/2] controller: " ogawa.yasufumi
2018-05-24 12:56 ` Ferruh Yigit [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=024f61be-c1fa-56f4-6602-fc331cb5402a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.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).