On Fri 2019-10-18 11:17:10, Kefeng Wang wrote: > There are pr_warning and pr_warng to show WARNING level message, > most of the code using pr_warn, number based on next-20191017, > > pr_warn: 5206 pr_warning: 546 (tools: 399, others: 147) > > Let's carry on with the work to standardize the logging macro, > kill pr_warning in the whole linux code. > > Patch[01-28]: simply sed and ajust formats
All these patches have been commited in printk.git, branch for-5.5-pr-warn. > patch[29]: drop pr_warning definition in printk > patch[33]: cleanup the checkpatch.pl I'll wait with these two until I am sure that the are no pr_warning() users in linux-next. > patch[30-32]: tools api/bpf/perf, rename and make manually changes Only the tool api patch is commited in printk.git. The other two (bpf and perf) will need to go via the related subsystems to avoid conflicts nightmare. The good thing is that these are userspace tools. They do not block removing pr_warning() from the internal kernel API. Best Regards, Petr
