From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples: fix CID 30699 copy-paste error
Date: Thu, 28 Apr 2016 10:39:05 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126479A6DCA@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1460548037-19585-1-git-send-email-slawomirx.mrozowicz@intel.com>
> -----Original Message-----
> From: Mrozowicz, SlawomirX
> Sent: Wednesday, April 13, 2016 12:47 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> <slawomirx.mrozowicz@intel.com>
> Subject: [PATCH] examples: fix CID 30699 copy-paste error
>
> It fix coverity issue:
> CID 30699 (#1 of 1): Copy-paste error (COPY_PASTE_ERROR)
> copy_paste_error: rx_port in pconf->rx_port looks like a copy-paste error.
>
> Fixes: de3cfa2c9823 ("sched: initial import")
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> ---
> examples/qos_sched/args.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/qos_sched/args.c b/examples/qos_sched/args.c
> index 3e7fd08..1916790 100644
> --- a/examples/qos_sched/args.c
> +++ b/examples/qos_sched/args.c
> @@ -270,7 +270,7 @@ app_parse_flow_conf(const char *conf_str)
> }
> if (pconf->tx_port >= RTE_MAX_ETHPORTS) {
> RTE_LOG(ERR, APP, "pfc %u: invalid tx port %"PRIu8"
> index\n",
> - nb_pfc, pconf->rx_port);
> + nb_pfc, pconf->tx_port);
> return -1;
> }
>
> --
> 1.9.1
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
prev parent reply other threads:[~2016-04-28 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 11:47 Slawomir Mrozowicz
2016-04-28 10:39 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D89126479A6DCA@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).