[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250207123706.727928-1-mrpre@163.com>
Date: Fri, 7 Feb 2025 20:37:05 +0800
From: Jiayuan Chen <mrpre@....com>
To: bpf@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
ast@...nel.org,
daniel@...earbox.net,
davem@...emloft.net,
kuba@...nel.org,
hawk@...nel.org,
john.fastabend@...il.com,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org,
qmo@...nel.org,
Jiayuan Chen <mrpre@....com>
Subject: [PATCH bpf-next v1 0/1] Using the right format specifiers for bpftool
Fixed some incorrect formatting specifiers that were exposed when I added
the "-Wformat" flag to the compiler options.
This patch doesn't include "-Wformat" in the Makefile for now, as I've
only addressed some obvious semantic issues with the compiler warnings.
There are still other warnings that need to be tackled.
For example, there's an ifindex that's sometimes defined as a signed type
and sometimes as an unsigned type, which makes formatting a real pain
- sometimes it needs %d and sometimes %u. This might require a more
fundamental fix from the variable definition side.
If the maintainer is okay with adding "-Wformat" to the
tools/bpf/bpftool/Makefile, please let us know, and we can follow up with
further fixes.
Jiayuan Chen (1):
bpftool: Using the right format specifiers
tools/bpf/bpftool/gen.c | 12 ++++++------
tools/bpf/bpftool/link.c | 14 +++++++-------
tools/bpf/bpftool/main.c | 8 ++++----
tools/bpf/bpftool/map.c | 10 +++++-----
4 files changed, 22 insertions(+), 22 deletions(-)
--
2.43.5
Powered by blists - more mailing lists