From: patchwork-bot+netdevbpf@kernel.org
To: Jiahao Xu <xujiahao@cmss.chinamobile.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] liquidio: enlarge the interrupt name buffer
Date: Wed, 11 Nov 2026 08:40:06 +0000 [thread overview]
Message-ID: <179438640618.794109.4972687983974562949.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106095114.3564335-1-xujiahao@cmss.chinamobile.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Fri, 6 Nov 2026 17:51:14 +0800 you wrote:
> The PF and VF interrupt names are assembled as "LiquidIO%u-pf%u-rxtx-%u"
> and "LiquidIO%u-vf%u-rxtx-%u" into INTRNAMSIZ (32-byte) slots. Three
> full-range %u do not fit, which gcc reports in a W=1 build:
>
> drivers/net/ethernet/cavium/liquidio/lio_core.c:1119:76: warning: '%u' directive output may be truncated writing between 1 and 10 bytes into a region of size between 0 and 13 [-Wformat-truncation=]
> drivers/net/ethernet/cavium/liquidio/lio_core.c:1124:76: warning: '%u' directive output may be truncated writing between 1 and 10 bytes into a region of size between 0 and 13 [-Wformat-truncation=]
>
> [...]
Here is the summary with links:
- [net-next] liquidio: enlarge the interrupt name buffer
https://git.kernel.org/netdev/net-next/c/1be1e065008d
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-11-11 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:51 [PATCH net-next] liquidio: enlarge the interrupt name buffer xujiahao
2026-11-11 8:40 ` 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=179438640618.794109.4972687983974562949.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xujiahao@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 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.