DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemming@brocade.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] Coverity policy for upstream (base) drivers.
Date: Thu, 12 Nov 2015 14:05:08 -0800	[thread overview]
Message-ID: <20151112140508.79489210@xeon-e3> (raw)

Looking at the Coverity scan for DPDK, it looks like all the base
drivers are marked to be ignored.

Although the changes to base drivers should not be done directly through
DPDK list. I think it is still valuable to have these driver scanned and
notify (badger) the vendors to fix there code.

Since lots of the bugs could be there, just blindly ignoring warnings
and issues is being naive.

             reply	other threads:[~2015-11-12 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 22:05 Stephen Hemminger [this message]
2015-11-12 22:18 ` Thomas Monjalon
2015-11-13  0:16   ` Mcnamara, John
2015-11-12 22:55 ` Matthew Hall
2015-11-13  0:12 ` Mcnamara, John
2015-11-13 18:49   ` Matthew Hall
2015-11-13 19:21     ` Mcnamara, John
2015-11-13 19:23       ` Matthew Hall
2015-11-13 19:38       ` Stephen Hemminger
2015-11-13 20:20         ` Matthew Hall

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=20151112140508.79489210@xeon-e3 \
    --to=shemming@brocade.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).