From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Luca Boccassi <bluca@debian.org>,
John McNamara <john.mcnamara@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 21/2/2019
Date: Thu, 21 Feb 2019 19:16:00 +0100 [thread overview]
Message-ID: <4357274.DFV0Bbj9Ng@xps> (raw)
In-Reply-To: <3eff7705bf6958382a727d35f786469a83479b1c.camel@debian.org>
21/02/2019 18:43, Luca Boccassi:
> On Thu, 2019-02-21 at 16:09 +0000, Ferruh Yigit wrote:
> > * Looking for suggestions from the community for a better or more
> > stable solutions
>
> The clang-based alternative I mentioned that can be used from
> Travis/Github is sonarcloud.io:
>
> https://sonarcloud.io/
>
> Here's an example implementation:
>
> https://github.com/zeromq/libzmq/commit/4d3516f634a4a5e3f522f5cb277da38b188d32eb
Another alternative platform: https://lgtm.com/
And a command line tool: https://fbinfer.com/
next prev parent reply other threads:[~2019-02-21 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 16:09 Ferruh Yigit
2019-02-21 16:19 ` Thomas Monjalon
2019-02-21 17:43 ` Luca Boccassi
2019-02-21 18:16 ` Thomas Monjalon [this message]
2019-03-06 15:27 ` Luca Boccassi
2019-03-06 15:45 ` Richardson, Bruce
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=4357274.DFV0Bbj9Ng@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--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).