RE: no printf in drivers code

[Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>]

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, February 3, 2023 7:57 AM
> To: Nicolas Chautru <nicolas.chautru@intel.com>; hemant.agrawal@nxp.com;
> Sachin Saxena <sachin.saxena@oss.nxp.com>; Gagandeep Singh
> <g.singh@nxp.com>; Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>;
> Bruce Richardson <bruce.richardson@intel.com>; Conor Walsh
> <conor.walsh@intel.com>; Chaoyong He <chaoyong.he@corigine.com>; Niklas
> Soderlund <niklas.soderlund@corigine.com>; Rasesh Mody
> <rmody@marvell.com>; Devendra Singh Rawat <dsinghrawat@marvell.com>;
> Jiawen Wu <jiawenwu@trustnetic.com>; Jian Wang
> <jianwang@trustnetic.com>; Rosen Xu <rosen.xu@intel.com>; Tianfei zhang
> <tianfei.zhang@intel.com>
> Cc: dev@dpdk.org; Ferruh Yigit <ferruh.yigit@amd.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; david.marchand@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.
>