From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, qmo@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, ast@kernel.org,
davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, mrpre@163.com
Subject: Re: [PATCH bpf-next v2 0/2] bpftool: Using the right format specifiers
Date: Mon, 17 Mar 2025 21:00:34 +0000 [thread overview]
Message-ID: <174224523451.3912314.17317997494330739760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250311112809.81901-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 11 Mar 2025 19:28:07 +0800 you wrote:
> This patch adds the -Wformat-signedness compiler flag to detect and
> prevent format string errors, where signed or unsigned types are
> mismatched with format specifiers. Additionally, it fixes some format
> string errors that were not fully addressed by the previous patch [1].
>
> [1] https://lore.kernel.org/bpf/20250207123706.727928-1-mrpre@163.com/T/#u
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpftool: Add -Wformat-signedness flag to detect format errors
https://git.kernel.org/bpf/bpf-next/c/8d86767be9c9
- [bpf-next,v2,2/2] bpftool: Using the right format specifiers
https://git.kernel.org/bpf/bpf-next/c/3775be3417cc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-17 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 11:28 [PATCH bpf-next v2 0/2] bpftool: Using the right format specifiers Jiayuan Chen
2025-03-11 11:28 ` [PATCH bpf-next v2 1/2] bpftool: Add -Wformat-signedness flag to detect format errors Jiayuan Chen
2025-03-11 11:28 ` [PATCH bpf-next v2 2/2] bpftool: Using the right format specifiers Jiayuan Chen
2025-03-17 21:00 ` patchwork-bot+netdevbpf [this message]
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=174224523451.3912314.17317997494330739760.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mrpre@163.com \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.