summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJeff Johnson <quic_jjohnson@quicinc.com>2024-04-16 19:41:19 +0300
committerKalle Valo <quic_kvalo@quicinc.com>2024-04-18 18:24:08 +0300
commit2372c6d28032b8336fb41c2dfa9209936cd27452 (patch)
treeb4aee3714e99e02f2dcde6e2b2049ec92df0a69c /tools/perf/scripts/python
parent0d55f86d0260bc167080374108d918fd523e3ee5 (diff)
downloadlinux-2372c6d28032b8336fb41c2dfa9209936cd27452.tar.xz
wifi: ath12k: don't use %pK in dmesg format strings
Currently, when debug logs are enabled, messages such as the following are found in the kernel log: event mgmt rx skb pK-error len 209 ftype 00 stype 50 The "pK-error" comes from using %pK to display an skb address in an interrupt context. Per the guidance in the current "printk-formats" documentation, %pK "is only intended when producing content of a file read by userspace from e.g. procfs or sysfs, not for dmesg." So replace %pK with %p in all of the ath12k_dbg() format strings. Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com> Link: https://msgid.link/20240416-pk-v1-1-2c8852743e6d@quicinc.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions