All of
 help / color / mirror / Atom feed
From: Thomas Monjalon <>
To: Stephen Hemminger <>
Subject: Re: Lgtm scan of DPDK
Date: Wed, 08 Jun 2022 10:22:36 +0200	[thread overview]
Message-ID: <5572850.DvuYhMxLoT@thomas> (raw)
In-Reply-To: <20220527161210.77212d0b@hermes.local>

28/05/2022 01:12, Stephen Hemminger:
> I just discovered that there is another tool similar to Coverity for scanning.
> It gives different results, and might be useful.
> The scans of github open source projects is already done.
> See:
> Shows 19 errors, 263 warnings and 111 recommendations.
> Of course, some of these are bogus. For example, tool thinks are scripts are Python 2.

The problem is that we already invest some time in Coverity triage
to mark false positives.
Can you check whether this tool has some false positives?

  reply	other threads:[~2022-06-08  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 23:12 Lgtm scan of DPDK Stephen Hemminger
2022-06-08  8:22 ` Thomas Monjalon [this message]
2022-06-08  8:35   ` Mcnamara, John
2022-06-09  2:36     ` Stephen Hemminger
2022-06-09 12:21       ` Mcnamara, John

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5572850.DvuYhMxLoT@thomas \ \ \ \ \ \

* 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.