From: Eduard Zingerman <eddyz87@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
kernel-team@fb.com, yonghong.song@linux.dev,
Eduard Zingerman <eddyz87@gmail.com>
Subject: [PATCH bpf-next v2 0/3] veristat: @files-list.txt notation for object files list
Date: Fri, 28 Feb 2025 16:01:44 -0800 [thread overview]
Message-ID: <20250301000147.1583999-1-eddyz87@gmail.com> (raw)
A few small veristat improvements:
- It is possible to hit command line parameters number limit,
e.g. when running veristat for all object files generated for
test_progs. This patch-set adds an option to read objects files list
from a file.
- Correct usage of strerror() function.
- Avoid printing log lines to CSV output.
Changelog:
- v1 -> v2:
- replace strerror(errno) with strerror(-err) in patch #2 (Andrii)
v1: https://lore.kernel.org/bpf/3ee39a16-bc54-4820-984a-0add2b5b5f86@gmail.com/T/
Eduard Zingerman (3):
veristat: @files-list.txt notation for object files list
veristat: strerror expects positive number (errno)
veristat: report program type guess results to sdterr
tools/testing/selftests/bpf/veristat.c | 70 +++++++++++++++++++++-----
1 file changed, 57 insertions(+), 13 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-01 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 0:01 Eduard Zingerman [this message]
2025-03-01 0:01 ` [PATCH bpf-next v2 1/3] veristat: @files-list.txt notation for object files list Eduard Zingerman
2025-03-01 0:01 ` [PATCH bpf-next v2 2/3] veristat: strerror expects positive number (errno) Eduard Zingerman
2025-03-01 0:01 ` [PATCH bpf-next v2 3/3] veristat: report program type guess results to sdterr Eduard Zingerman
2025-03-03 22:00 ` [PATCH bpf-next v2 0/3] veristat: @files-list.txt notation for object files list patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250301000147.1583999-1-eddyz87@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox