From: "Mcnamara, John" <john.mcnamara@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, "Stokes, Ian" <ian.stokes@intel.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Akhil, Goyal" <akhil.goyal@nxp.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Yongseok Koh <yskoh@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Shahaf Shuler" <shahafs@mellanox.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
Date: Mon, 1 Apr 2019 15:47:37 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F5BB230@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8ymYaW9CfQc6Mquu4Jc_U70KLvoXghp6LVXTb_hn8fu3A@mail.gmail.com>
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
>
> On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Coverity
> --------
>
> * Coverity is back on, John run a new scan with latest code:
> https://scan.coverity.com/projects/dpdk-data-plane-development-kit
>
> The "components" mappings seem quite old/invalid to me:
> - we still have the old pmds path à la lib/librte_pmd_XXX
> - pmd_bond points to an drivers/net/bond/.
> - pmd_mlx4 points to drivers/net/ixgbe/.
>
> And others catches almost everything (400k loc).
>
> John, can you fix it?
Yes. Let me know the mappings/changes you want to make and I can implement them or we can make you and admin and you can do it.
John
next prev parent reply other threads:[~2019-04-01 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 12:03 Ferruh Yigit
2019-03-28 12:03 ` Ferruh Yigit
2019-03-28 12:48 ` David Marchand
2019-03-28 12:48 ` David Marchand
2019-04-01 15:47 ` Mcnamara, John [this message]
2019-04-01 15:47 ` Mcnamara, John
2019-04-01 19:10 ` David Marchand
2019-04-01 19:10 ` David Marchand
2019-04-02 9:35 ` Bruce Richardson
2019-04-02 9:35 ` Bruce Richardson
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=B27915DBBA3421428155699D51E4CFE23F5BB230@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).