From: Thomas Monjalon <thomas@monjalon.net>
To: "Wu, Yanglong" <yanglong.wu@intel.com>
Cc: dev@dpdk.org, "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Yang, Zhiyong" <zhiyong.yang@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3] app/testpmd: fix port_id alloction issue
Date: Wed, 10 Jan 2018 00:27:04 +0100 [thread overview]
Message-ID: <2624486.knYaX70hJV@xps> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B709BF3@shsmsx102.ccr.corp.intel.com>
> > 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")
Cc: stable@dpdk.org
> > 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>
Applied, thanks
parent reply other threads:[~2018-01-09 23:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6A0DE07E22DDAD4C9103DF62FEBC09093B709BF3@shsmsx102.ccr.corp.intel.com>]
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=2624486.knYaX70hJV@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--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).