From: patchwork-bot+netdevbpf@kernel.org
To: Zhu Jun <zhujun2@cmss.chinamobile.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] tools/bpf:Fix the wrong format specifier
Date: Tue, 30 Jul 2024 20:50:32 +0000 [thread overview]
Message-ID: <172237263295.10299.13717406365394258197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240724111120.11625-1-zhujun2@cmss.chinamobile.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 24 Jul 2024 04:11:20 -0700 you wrote:
> The format specifier of "unsigned int" in printf() should be "%u", not
> "%d".
>
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
> ---
> Changes:
> v2:
> modify commit info
> v3:
> fix compile warning
> v4:
> Thanks! But unsigned seems relevant here, and it doesn't make much sense
> to change the type of the int just because we don't have the right
> specifier in the printf(), does it? Sorry, I should have been more
> explicit: the warning on v1 and v2 can be addressed by simply removing
> the "space flag" from the format string, in other words:
>
> [...]
Here is the summary with links:
- [v4] tools/bpf:Fix the wrong format specifier
https://git.kernel.org/bpf/bpf-next/c/781f0bbbdade
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:[~2024-07-30 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 11:11 [PATCH v4] tools/bpf:Fix the wrong format specifier Zhu Jun
2024-07-24 13:44 ` Quentin Monnet
2024-07-24 15:43 ` [PATCH v4] tools/bpf: Fix " Markus Elfring
2024-07-24 15:59 ` Quentin Monnet
2024-07-24 16:26 ` [v4] " Markus Elfring
2024-07-30 20:50 ` 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=172237263295.10299.13717406365394258197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=zhujun2@cmss.chinamobile.com \
/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