From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <horms@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sgoutham@marvell.com, gakula@marvell.com,
sbhatta@marvell.com, hkelam@marvell.com,
dan.carpenter@linaro.org, netdev@vger.kernel.org, andrew@lunn.ch
Subject: Re: [PATCH net-next v2] octeontx2-pf: Treat truncation of IRQ name as an error
Date: Tue, 07 May 2024 02:10:26 +0000 [thread overview]
Message-ID: <171504782656.18663.926414916456400043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240503-octeon2-pf-irq_name-truncation-v2-1-91099177b942@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 03 May 2024 12:11:58 +0100 you wrote:
> According to GCC, the constriction of irq_name in otx2_open()
> may, theoretically, be truncated.
>
> This patch takes the approach of treating such a situation as an error
> which it detects by making use of the return value of snprintf, which is
> the total number of bytes, excluding the trailing '\0', that would have
> been written.
>
> [...]
Here is the summary with links:
- [net-next,v2] octeontx2-pf: Treat truncation of IRQ name as an error
https://git.kernel.org/netdev/net-next/c/6bee69422590
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-05-07 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 11:11 [PATCH net-next v2] octeontx2-pf: Treat truncation of IRQ name as an error Simon Horman
2024-05-07 2:10 ` 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=171504782656.18663.926414916456400043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).