From: patchwork-bot+netdevbpf@kernel.org
To: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests: net: csum: Fix printk format in recv_get_packet_csum_status()
Date: Mon, 19 Jan 2026 18:20:15 +0000 [thread overview]
Message-ID: <176884681553.87873.17149819008459175901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8b69b40826553c1dd500d9d25e45883744f3f348.1768556791.git.chleroy@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Jan 2026 10:48:55 +0100 you wrote:
> Following warning is encountered when building selftests on powerpc/32.
>
> CC csum
> csum.c: In function 'recv_get_packet_csum_status':
> csum.c:710:50: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
> 710 | error(1, 0, "cmsg: len=%lu expected=%lu",
> | ~~^
> | |
> | long unsigned int
> | %u
> 711 | cm->cmsg_len, CMSG_LEN(sizeof(struct tpacket_auxdata)));
> | ~~~~~~~~~~~~
> | |
> | size_t {aka unsigned int}
> csum.c:710:63: warning: format '%lu' expects argument of type 'long unsigned int', but argument 5 has type 'unsigned int' [-Wformat=]
> 710 | error(1, 0, "cmsg: len=%lu expected=%lu",
> | ~~^
> | |
> | long unsigned int
> | %u
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: net: csum: Fix printk format in recv_get_packet_csum_status()
https://git.kernel.org/netdev/net-next/c/d321d505edb6
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:[~2026-01-19 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:48 [PATCH net-next v2] selftests: net: csum: Fix printk format in recv_get_packet_csum_status() Christophe Leroy (CS GROUP)
2026-01-16 10:13 ` Maxime Chevallier
2026-01-19 18:20 ` 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=176884681553.87873.17149819008459175901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chleroy@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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