[dpdk-dev] DPDK Release Status Meeting 28/3/2019
Mcnamara, John
john.mcnamara at intel.com
Mon Apr 1 17:47:37 CEST 2019
> From: David Marchand [mailto:david.marchand at redhat.com]
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit at intel.com>; Mcnamara, John <john.mcnamara at intel.com>
> Cc: dpdk-dev <dev at dpdk.org>; Stokes, Ian <ian.stokes at intel.com>; Thomas Monjalon <thomas at monjalon.net>; Jerin Jacob <jerin.jacob at caviumnetworks.com>; Akhil, Goyal <akhil.goyal at nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu at intel.com>; Xu, Qian Q <qian.q.xu at intel.com>; Yongseok Koh <yskoh at mellanox.com>; Maxime Coquelin <maxime.coquelin at redhat.com>; Zhang, Qi Z <qi.z.zhang at intel.com>; Shahaf Shuler <shahafs at mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch at 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 at 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
More information about the dev
mailing list