> -----Original Message-----
> From: Thomas Monjalon <tho...@monjalon.net>
> Sent: Friday, February 3, 2023 7:57 AM
> To: Nicolas Chautru <nicolas.chau...@intel.com>; hemant.agra...@nxp.com;
> Sachin Saxena <sachin.sax...@oss.nxp.com>; Gagandeep Singh
> <g.si...@nxp.com>; Sunil Uttarwar <sunilprakashrao.uttar...@amd.com>;
> Bruce Richardson <bruce.richard...@intel.com>; Conor Walsh
> <conor.wa...@intel.com>; Chaoyong He <chaoyong...@corigine.com>; Niklas
> Soderlund <niklas.soderl...@corigine.com>; Rasesh Mody
> <rm...@marvell.com>; Devendra Singh Rawat <dsinghra...@marvell.com>;
> Jiawen Wu <jiawe...@trustnetic.com>; Jian Wang
> <jianw...@trustnetic.com>; Rosen Xu <rosen...@intel.com>; Tianfei zhang
> <tianfei.zh...@intel.com>
> Cc: dev@dpdk.org; Ferruh Yigit <ferruh.yi...@amd.com>; Andrew Rybchenko
> <andrew.rybche...@oktetlabs.ru>; david.march...@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.
>
