no printf in drivers code

[Honnappa Nagarahalli]

> -----Original Message-----
> From: Thomas Monjalon <thomas at monjalon.net>
> Sent: Friday, February 3, 2023 7:57 AM
> To: Nicolas Chautru <nicolas.chautru at intel.com>; hemant.agrawal at nxp.com;
> Sachin Saxena <sachin.saxena at oss.nxp.com>; Gagandeep Singh
> <g.singh at nxp.com>; Sunil Uttarwar <sunilprakashrao.uttarwar at amd.com>;
> Bruce Richardson <bruce.richardson at intel.com>; Conor Walsh
> <conor.walsh at intel.com>; Chaoyong He <chaoyong.he at corigine.com>; Niklas
> Soderlund <niklas.soderlund at corigine.com>; Rasesh Mody
> <rmody at marvell.com>; Devendra Singh Rawat <dsinghrawat at marvell.com>;
> Jiawen Wu <jiawenwu at trustnetic.com>; Jian Wang
> <jianwang at trustnetic.com>; Rosen Xu <rosen.xu at intel.com>; Tianfei zhang
> <tianfei.zhang at intel.com>
> Cc: dev at dpdk.org; Ferruh Yigit <ferruh.yigit at amd.com>; Andrew Rybchenko
> <andrew.rybchenko at oktetlabs.ru>; david.marchand at redhat.com
> Subject: no printf in drivers code
> 
> Hello,
> 
> We have too many drivers using printf() instead of rte_log().
> Please propose a plan to replace or remove the calls to printf().
> If no plan, I could propose one but you may not like it :)
Does it make sense to add scripts to CI to capture this issue? In general, we do not want printfs in DPDK code (other than tests, sample apps?)

> 
> Affected drivers are:
> 	baseband/acc
> 	bus/dpaa
> 	bus/fslmc
> 	crypto/caam_jr
> 	crypto/ccp
> 	dma/ioat
> 	net/dpaa
> 	net/dpaa2
> 	net/nfp
> 	net/qede
> 	net/txgbe
> 	raw/ifpga
> 
> PS: printf is allowed for tests and dumps.
>