From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hariprasad Govindharajan <hariprasad.govindharajan@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org, stephen@networkplumber.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v3] app/testpmd: fix return value in portlist parser
Date: Thu, 20 Feb 2020 20:41:11 +0000 [thread overview]
Message-ID: <3762664c-6e1c-8b55-8a77-7981601fb0cb@intel.com> (raw)
In-Reply-To: <1582220343-22149-1-git-send-email-hariprasad.govindharajan@intel.com>
On 2/20/2020 5:39 PM, Hariprasad Govindharajan wrote:
> The function parse_port_list() is designed to return
> unsigned int value. After sanitizing the inputs,
> it is returning -1. Changed it to return 0.
>
> Fixes: 2df00d562d20 ("app/testpmd: add --portlist option")
> Cc: hariprasad.govindharajan@intel.com
>
> Signed-off-by: Hariprasad Govindharajan <hariprasad.govindharajan@intel.com>
(Carrying ack from previous version)
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-02-20 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 13:26 [dpdk-dev] [PATCH] app/testpmd: fix wrong return value in parse_port_list Hariprasad Govindharajan
2020-02-20 15:29 ` Iremonger, Bernard
2020-02-20 15:43 ` [dpdk-dev] [PATCH v2] app/testpmd: fix return value in portlist parser Hariprasad Govindharajan
2020-02-20 15:46 ` Govindharajan, Hariprasad
2020-02-20 17:01 ` Ferruh Yigit
2020-02-20 17:39 ` [dpdk-dev] [PATCH v3] " Hariprasad Govindharajan
2020-02-20 20:41 ` Ferruh Yigit [this message]
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=3762664c-6e1c-8b55-8a77-7981601fb0cb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hariprasad.govindharajan@intel.com \
--cc=jingjing.wu@intel.com \
--cc=stephen@networkplumber.org \
--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).