From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>
Cc: dev@dpdk.org, "Dumitrescu,
Cristian" <cristian.dumitrescu@intel.com>,
"Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] examples/qos_sched: fix copy-paste error
Date: Mon, 16 May 2016 18:16:17 +0200 [thread overview]
Message-ID: <2073820.rIF6IQjRlm@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126479A6ED9@IRSMSX108.ger.corp.intel.com>
copy-paste is the cause of this error.
The headline should show which error is fixed (or briefly its impact area).
Here: "fix error message"
> > Fix issue reported by Coverity.
> >
> > Coverity ID 30699: 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>
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks
next prev parent reply other threads:[~2016-05-16 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 13:08 [dpdk-dev] [PATCH v3] examples/qos_sched: fix negative loop bound Michal Jastrzebski
2016-04-21 13:08 ` [dpdk-dev] [PATCH v3] examples/qos_sched: fix copy-paste error Michal Jastrzebski
2016-04-28 11:00 ` Dumitrescu, Cristian
2016-05-16 16:16 ` Thomas Monjalon [this message]
2016-04-21 13:08 ` [dpdk-dev] [PATCH v3] examples/qos_sched: fix bad bit shift operation Michal Jastrzebski
2016-04-28 11:16 ` Dumitrescu, Cristian
2016-05-10 9:39 ` Mrozowicz, SlawomirX
2016-05-10 9:45 ` Dumitrescu, Cristian
2016-04-28 10:59 ` [dpdk-dev] [PATCH v3] examples/qos_sched: fix negative loop bound Dumitrescu, Cristian
2016-05-16 16:02 ` 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=2073820.rIF6IQjRlm@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=michalx.k.jastrzebski@intel.com \
--cc=roy.fan.zhang@intel.com \
--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).