From: patchwork-bot+netdevbpf@kernel.org
To: Nikhil P. Rao <nikhil.rao@amd.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, brett.creeley@amd.com,
eric.joyner@amd.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net v2] pds_core: ensure null-termination for firmware version strings
Date: Thu, 21 May 2026 15:30:10 +0000 [thread overview]
Message-ID: <177937741014.384060.2930118060876469975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260520205842.1486718-1-nikhil.rao@amd.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 20:58:42 +0000 you wrote:
> The driver passes fw_version directly to devlink_info_version_stored_put()
> without ensuring null-termination. While current firmware null-terminates
> these strings, the driver should not rely on this behavior. Add explicit
> null-termination to prevent potential issues if firmware behavior changes.
>
> Fixes: 45d76f492938 ("pds_core: set up device and adminq")
> Assisted-by: Claude:claude-opus-4
> Signed-off-by: Nikhil P. Rao <nikhil.rao@amd.com>
>
> [...]
Here is the summary with links:
- [net,v2] pds_core: ensure null-termination for firmware version strings
https://git.kernel.org/netdev/net/c/3d4432d34c19
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-05-21 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 20:58 [PATCH net v2] pds_core: ensure null-termination for firmware version strings Nikhil P. Rao
2026-05-21 15: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=177937741014.384060.2930118060876469975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.rao@amd.com \
--cc=pabeni@redhat.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