> From: David Marchand [mailto:david.march...@redhat.com] 
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yi...@intel.com>; Mcnamara, John 
> <john.mcnam...@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.sto...@intel.com>; Thomas 
> Monjalon <tho...@monjalon.net>; Jerin Jacob <jerin.ja...@caviumnetworks.com>; 
> Akhil, Goyal <akhil.go...@nxp.com>; Dumitrescu, Cristian 
> <cristian.dumitre...@intel.com>; Xu, Qian Q <qian.q...@intel.com>; Yongseok 
> Koh <ys...@mellanox.com>; Maxime Coquelin <maxime.coque...@redhat.com>; 
> Zhang, Qi Z <qi.z.zh...@intel.com>; Shahaf Shuler <shah...@mellanox.com>; De 
> Lara Guarch, Pablo <pablo.de.lara.gua...@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.yi...@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


Reply via email to