From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: Re: [draft] DPDK Release Status Meeting 11/10/2018
Date: Thu, 11 Oct 2018 13:31:03 +0100 [thread overview]
Message-ID: <5fbdfd9f-3e73-4eca-d497-9d73cd88401b@intel.com> (raw)
In-Reply-To: <1d374c5f-7323-d3f4-a48d-6ef82afebc40@intel.com>
On 10/11/2018 12:32 PM, Ferruh Yigit wrote:
> Minutes 11 October 2018
> ----------------------
...
> Coverity
> --------
> * Coverity is broken for DPDK
> * John is doing manual Coverity builds and upload, analysis not working
> * Ferruh will try next-net Coverity project
I tried with next-net project and it worked:
https://scan.coverity.com/projects/dpdk-next-net
prev parent reply other threads:[~2018-10-11 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 11:32 [draft] DPDK Release Status Meeting 11/10/2018 Ferruh Yigit
2018-10-11 12:31 ` Ferruh Yigit [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=5fbdfd9f-3e73-4eca-d497-9d73cd88401b@intel.com \
--to=ferruh.yigit@intel.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.