From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/qos_sched: fix uninitialized scalar variable
Date: Tue, 24 Oct 2017 08:41:29 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6D33278ED9@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <9dc9d7ef-f238-08cc-c970-819419185d90@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, October 23, 2017 5:32 PM
> To: Singh, Jasvinder <jasvinder.singh@intel.com>; dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] examples/qos_sched: fix uninitialized scalar
> variable
>
> On 10/23/2017 3:36 AM, Jasvinder Singh wrote:
> > Fix problem with uninitialized rx/tx deferred_start flags of the
> > struct rte_eth_rxconf/txconf by initializing with 0 value (deferred
> > start of the rx/tx queues is turned off). This setting allows device
> > rx/tx queues to start with rte_eth_dev_start().
> >
> > CID 194999 (#1 of 1): Uninitialized scalar variable (UNINIT) CID
> > 195009 (#1 of 1): Uninitialized scalar variable (UNINIT)
>
> Is this Coverity ID? If so we have a defined format for it:
Yes, this is coverity issue.
> Coverity issue: xxxxxx
> Fixes: yyyyyyyyyyyy ("..................")
> Cc: stable@dpdk.org [if required]
>
> Signed-off-by: .....
>
Ok, I will resend the patch.
next prev parent reply other threads:[~2017-10-24 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 10:36 Jasvinder Singh
2017-10-23 16:31 ` Ferruh Yigit
2017-10-24 8:41 ` Singh, Jasvinder [this message]
2017-10-24 9:09 ` Jasvinder Singh
2017-10-24 21:58 ` 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=54CBAA185211B4429112C315DA58FF6D33278ED9@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@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).