> -----Original Message-----
> From: Thomas Monjalon <[email protected]>
> Sent: Friday, February 3, 2023 7:57 AM
> To: Nicolas Chautru <[email protected]>; [email protected];
> Sachin Saxena <[email protected]>; Gagandeep Singh
> <[email protected]>; Sunil Uttarwar <[email protected]>;
> Bruce Richardson <[email protected]>; Conor Walsh
> <[email protected]>; Chaoyong He <[email protected]>; Niklas
> Soderlund <[email protected]>; Rasesh Mody
> <[email protected]>; Devendra Singh Rawat <[email protected]>;
> Jiawen Wu <[email protected]>; Jian Wang
> <[email protected]>; Rosen Xu <[email protected]>; Tianfei zhang
> <[email protected]>
> Cc: [email protected]; Ferruh Yigit <[email protected]>; Andrew Rybchenko
> <[email protected]>; [email protected]
> 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.
>
