From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Remy Horton <remy.horton@intel.com>, dev@dpdk.org
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>, Jingjing Wu <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] testpmd: fix incorrect port_id word size
Date: Sat, 20 Jan 2018 13:33:54 +0000 [thread overview]
Message-ID: <fb0957ca-874e-a81a-af66-659f3d880c0c@intel.com> (raw)
In-Reply-To: <20180119132722.11120-1-remy.horton@intel.com>
On 1/19/2018 1:27 PM, Remy Horton wrote:
"app/testpmd: fix incorrect port id word size" ?
> The word size of port_id is now 16 bits, but there were parsing directives
> that assumed it was still of type UINT8, resulting in incorrect commandline
> parse results.
>
> Fixes: f14a210a65fe ("app: fix port id type")
Cc: stable@dpdk.org
> Signed-off-by: Remy Horton <remy.horton@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-01-20 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 13:27 Remy Horton
2018-01-20 13:33 ` Ferruh Yigit [this message]
2018-01-31 22:22 ` 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=fb0957ca-874e-a81a-af66-659f3d880c0c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=remy.horton@intel.com \
--cc=wenzhuo.lu@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).