DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] Coverity project created for dpdk-next-net tree
Date: Fri, 17 Feb 2017 11:08:22 +0000	[thread overview]
Message-ID: <c821bcf4-d865-6cf6-76ab-5f1de9bda743@intel.com> (raw)
In-Reply-To: <38c36ee3-48be-0387-0c17-239685481459@intel.com>

On 1/11/2017 6:57 PM, Ferruh Yigit wrote:
> On 11/21/2016 11:29 PM, Ferruh Yigit wrote:
>> Coverity project created for dpdk-next-net tree:
>> https://scan.coverity.com/projects/dpdk-next-net
>>
>> This can be useful to fix coverity issues before next-net merged into
>> master branch.
>>
>> Project is open for everyone to register and to get scan reports, there
>> will be regular scans for next-net tree.
>>
>> Specially driver maintainers, please consider registering to the project
>> and checking your driver's defect status.
>> I believe there are some false positives, it is appreciated if you can
>> identify and mark them in coverity tool.
>>
>> PS: As a reminder, a coverity project already exists for main dpdk repo:
>> https://scan.coverity.com/projects/dpdk-data-plane-development-kit
>>
> 
> Reminder of the next-net coverity project.
> Project kept up to date with new driver patches merged in.
> 
> Driver maintainers can check and fix issues introduced in next-net
> before sub-tree merged into main tree.

A new coverity scan done for next-net tree for 17.02 release:
https://scan.coverity.com/projects/dpdk-next-net?tab=overview

Driver maintainers, please consider fixing existing defects before
adding more code into 17.05 release.


Thanks,
ferruh

      reply	other threads:[~2017-02-17 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 23:29 Ferruh Yigit
2017-01-11 18:57 ` Ferruh Yigit
2017-02-17 11:08   ` 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=c821bcf4-d865-6cf6-76ab-5f1de9bda743@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    /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).