From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <horms@kernel.org>
Cc: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, morbo@google.com,
daniel.machon@microchip.com, f.fainelli@gmail.com,
jiawenwu@trustnetic.com, justinstitt@google.com,
mengyuanlou@net-swift.com, nathan@kernel.org,
ndesaulniers@google.com, richardcochran@gmail.com,
olteanv@gmail.com, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: String format safety updates
Date: Tue, 15 Oct 2024 18:00:39 +0000 [thread overview]
Message-ID: <172901523973.1243233.15115211719857915822.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241014-string-thing-v2-0-b9b29625060a@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Oct 2024 09:52:24 +0100 you wrote:
> Hi,
>
> This series addresses string format safety issues that are
> flagged by tooling in files touched by recent patches.
>
> I do not believe that any of these issues are bugs.
> Rather, I am providing these updates as I think there is a value
> in addressing such warnings so real problems stand out.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: dsa: microchip: copy string using strscpy
https://git.kernel.org/netdev/net-next/c/26919411acfa
- [net-next,v2,2/2] net: txgbe: Pass string literal as format argument of alloc_workqueue()
https://git.kernel.org/netdev/net-next/c/d6488e77725e
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-10-15 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 8:52 Simon Horman
2024-10-14 8:52 ` [PATCH net-next v2 1/2] net: dsa: microchip: copy string using strscpy Simon Horman
2024-10-14 8:52 ` [PATCH net-next v2 2/2] net: txgbe: Pass string literal as format argument of alloc_workqueue() Simon Horman
2024-10-15 18:00 ` 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=172901523973.1243233.15115211719857915822.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=jiawenwu@trustnetic.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mengyuanlou@net-swift.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=woojung.huh@microchip.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
all inboxes | Powered by JetHome®