From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: sgoutham@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, darren.kenny@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: thunderx: Fix format-truncation warning in bgx_acpi_match_id()
Date: Tue, 15 Jul 2025 00:30:27 +0000 [thread overview]
Message-ID: <175253942775.4037397.6464344303980348898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711140532.2463602-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 11 Jul 2025 07:05:30 -0700 you wrote:
> The buffer bgx_sel used in snprintf() was too small to safely hold
> the formatted string "BGX%d" for all valid bgx_id values. This caused
> a -Wformat-truncation warning with `Werror` enabled during build.
>
> Increase the buffer size from 5 to 7 and use `sizeof(bgx_sel)` in
> snprintf() to ensure safety and suppress the warning.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: thunderx: Fix format-truncation warning in bgx_acpi_match_id()
https://git.kernel.org/netdev/net-next/c/53d20606c406
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-07-15 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 14:05 [PATCH net-next v3] net: thunderx: Fix format-truncation warning in bgx_acpi_match_id() Alok Tiwari
2025-07-15 0:30 ` 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=175253942775.4037397.6464344303980348898.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=darren.kenny@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.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.