From: Ferruh Yigit <ferruh.yigit@intel.com>
To: DPDK <dev@dpdk.org>, Yong Wang <yongwang@vmware.com>,
John McNamara <john.mcnamara@intel.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Declan Doherty <declan.doherty@intel.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Harish Patil <harish.patil@qlogic.com>,
Helin Zhang <helin.zhang@intel.com>,
Huawei Xie <huawei.xie@intel.com>,
Jakub Palider <jpa@semihalf.com>, Jan Medala <jan@semihalf.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Jing Chen <jing.d.chen@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
John Daley <johndale@cisco.com>,
"John W. Linville" <linville@tuxdriver.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Maciej Czekaj <maciej.czekaj@caviumnetworks.com>,
Matej Vido <matejvido@gmail.com>,
Nelson Escobar <neescoba@cisco.com>,
Netanel Belgazal <netanel
Subject: Coverity project created for dpdk-next-net tree
Date: Mon, 21 Nov 2016 23:29:48 +0000 [thread overview]
Message-ID: <be82169c-6af3-4dff-1729-9e07c06d4c19@intel.com> (raw)
Coverity project created for dpdk-next-net tree:
https://scan.coverity.com/projects/dpdk-next-net
This can be useful to fix coverity issues before next-net merged into
master branch.
Project is open for everyone to register and to get scan reports, there
will be regular scans for next-net tree.
Specially driver maintainers, please consider registering to the project
and checking your driver's defect status.
I believe there are some false positives, it is appreciated if you can
identify and mark them in coverity tool.
Thanks,
ferruh
PS: As a reminder, a coverity project already exists for main dpdk repo:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit
next reply other threads:[~2016-11-21 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 23:29 Ferruh Yigit [this message]
2017-01-11 18:57 ` Coverity project created for dpdk-next-net tree Ferruh Yigit
2017-02-17 11:08 ` Ferruh Yigit
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=be82169c-6af3-4dff-1729-9e07c06d4c19@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alejandro.lucero@netronome.com \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=harish.patil@qlogic.com \
--cc=helin.zhang@intel.com \
--cc=huawei.xie@intel.com \
--cc=jan@semihalf.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.com \
--cc=jpa@semihalf.com \
--cc=konstantin.ananyev@intel.com \
--cc=linville@tuxdriver.com \
--cc=maciej.czekaj@caviumnetworks.com \
--cc=matejvido@gmail.com \
--cc=neescoba@cisco.com \
--cc=yongwang@vmware.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