From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Zhiyong Yang <zhiyong.yang@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org, orika@mellanox.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] examples/flow_filtering: fix incorrect port id size
Date: Thu, 25 Jan 2018 14:05:16 +0000 [thread overview]
Message-ID: <1f4e3918-4380-f905-c35c-18fda4646061@intel.com> (raw)
In-Reply-To: <20180124061006.38304-1-zhiyong.yang@intel.com>
On 1/24/2018 6:10 AM, Zhiyong Yang wrote:
> Ethdev port id has been extended 16bits from 8bits in DPDK 17.11 release,
> the patch fixes mismatch use.
>
> Fixes: 4a3ef59a10c8 ("examples/flow_filtering: add simple demo of flow API")
> Cc: stable@dpdk.org
> Cc: orika@mellanox.com
> Cc: ferruh.yigit@intel.com
> Cc: thomas@monjalon.net
>
> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-01-25 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 6:10 Zhiyong Yang
2018-01-25 14:05 ` Ferruh Yigit [this message]
2018-01-25 14:11 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=1f4e3918-4380-f905-c35c-18fda4646061@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zhiyong.yang@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 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).