From: Stephen Hemminger <shemming@brocade.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Coverity policy for upstream (base) drivers.
Date: Fri, 13 Nov 2015 11:38:22 -0800 [thread overview]
Message-ID: <20151113113822.1541d4dd@xeon-e3> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2023BBD21@IRSMSX103.ger.corp.intel.com>
On Fri, 13 Nov 2015 19:21:24 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:
> > -----Original Message-----
> > From: Matthew Hall [mailto:mhall@mhcomputing.net]
> > Sent: Friday, November 13, 2015 6:49 PM
> > To: Mcnamara, John
> > Cc: Stephen Hemminger; Thomas Monjalon; dev@dpdk.org
> > Subject: Re: [dpdk-dev] Coverity policy for upstream (base) drivers.
> >
> > On Fri, Nov 13, 2015 at 12:12:04AM +0000, Mcnamara, John wrote:
> > > If people haven't already done so I would urge them to sign up and
> > view/fix the defects.
> > >
> > > https://scan.coverity.com/users/sign_up
> > > https://scan.coverity.com/projects/4005 (DPDK)
> >
> > Hi John,
> >
> > I got signed up. Thanks for spearheading this.
> >
> > From past experience squashing SA defects on my own code and several
> > previous employers I would like to recommend we band together and
> > configure a SonarQube instance.
>
> Hi Matthew,
>
> I definitely be interested in getting SonarQube working with DPDK. We can sync up on this as soon as the 2.2 bush fires die down.
>
> John.
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.
next prev parent reply other threads:[~2015-11-13 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 22:05 Coverity policy for upstream (base) drivers 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 [this message]
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=20151113113822.1541d4dd@xeon-e3 \
--to=shemming@brocade.com \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.