From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Zhiyong" <zhiyong.yang@intel.com>,
"Wu, Yanglong" <yanglong.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/testpmd: fix port_id alloction issue
Date: Fri, 5 Jan 2018 00:58:03 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B709BF3@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20180102053542.128402-1-yanglong.wu@intel.com>
Hi,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yanglong Wu
> Sent: Tuesday, January 2, 2018 1:36 PM
> To: dev@dpdk.org
> Cc: Yang, Zhiyong <zhiyong.yang@intel.com>; Wu, Yanglong
> <yanglong.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v3] app/testpmd: fix port_id alloction issue
>
> 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>
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
next prev parent reply other threads:[~2018-01-05 0:58 UTC|newest]
Thread overview: 11+ 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
2018-01-02 5:35 ` [dpdk-dev] [PATCH v3] " Yanglong Wu
2018-01-05 0:58 ` Lu, Wenzhuo [this message]
2018-01-09 23:27 ` Thomas Monjalon
2018-02-05 2:33 [dpdk-dev] [PATCH v2] app/testpmd:vlan filter fail Yanglong Wu
2018-02-05 7:53 ` [dpdk-dev] [PATCH v3] app/testpmd: fix port_id alloction issue Yanglong Wu
2018-02-05 8:00 ` Yang, Zhiyong
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=6A0DE07E22DDAD4C9103DF62FEBC09093B709BF3@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@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).