From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <shemming@brocade.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Coverity policy for upstream (base) drivers.
Date: Fri, 13 Nov 2015 15:20:18 -0500 [thread overview]
Message-ID: <20151113202018.GA28919@mhcomputing.net> (raw)
In-Reply-To: <20151113113822.1541d4dd@xeon-e3>
On Fri, Nov 13, 2015 at 11:38:22AM -0800, Stephen Hemminger wrote:
> It looked like SonarQube was both non-free for doing any real scans,
> and the default C rules were oriented towards a completely different
> Windows oriented coding style.
I was using the free version to do SA dashboad for a team of several hundred
previously.
But it's possible they made licensing changes since I last used it.
If you have any thoughts about better freer dashboards I am all ears.
Just trying to get some good tooling in place to deal w/ exponential growth of
DPDK code.
Matthew.
prev parent reply other threads:[~2015-11-13 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 22:05 Stephen Hemminger
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 [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=20151113202018.GA28919@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=shemming@brocade.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).