From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yanglong Wu <yanglong.wu@intel.com>, dev@dpdk.org
Cc: zhiyong.yang@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix port_id alloction issue
Date: Fri, 22 Dec 2017 16:04:02 -0800 [thread overview]
Message-ID: <00a3761e-e5b8-9768-100b-696b06e962fe@intel.com> (raw)
In-Reply-To: <20171222074807.122265-1-yanglong.wu@intel.com>
On 12/21/2017 11:48 PM, Yanglong Wu wrote:
> In the feature of increasing port_id range from 8 bits to 16 bits,
> vlan port_id allocation function was forget to substitute UINT8 with
> UINT16, so the vlan port_id was allocated as a inccrete number.
>
> Fixes:28caa76aea71 ("app/testpmd: fix port id type")
>
> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
Reviewed-by: Zhiyong Yang <zhiyong.yang@intel.com>
(carrying existing review tag)
next prev parent reply other threads:[~2017-12-23 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 1:26 [dpdk-dev] [PATCH] " Yanglong Wu
2017-11-23 1:57 ` Yang, Zhiyong
2017-11-23 2:05 ` Yang, Zhiyong
2017-12-22 6:45 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2017-12-22 7:48 ` Yanglong Wu
2017-12-23 0:04 ` Ferruh Yigit [this message]
2018-01-02 5:35 ` [dpdk-dev] [PATCH v3] " Yanglong Wu
2018-01-05 0:58 ` Lu, Wenzhuo
2018-01-09 23:27 ` Thomas Monjalon
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=00a3761e-e5b8-9768-100b-696b06e962fe@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=yanglong.wu@intel.com \
--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).