From: patchwork-bot+netdevbpf@kernel.org
To: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
Cc: willemdebruijn.kernel@gmail.com, kernelxing@tencent.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests/net: initialize char variable to null
Date: Thu, 27 Nov 2025 00:30:06 +0000 [thread overview]
Message-ID: <176420340676.1898314.13893932035551539532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125165302.20079-1-ankitkhushwaha.linux@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Nov 2025 22:23:02 +0530 you wrote:
> char variable in 'so_txtime.c' & 'txtimestamp.c' were left uninitilized
> when switch default case taken. which raises following warning.
>
> txtimestamp.c:240:2: warning: variable 'tsname' is used uninitialized
> whenever switch default is taken [-Wsometimes-uninitialized]
>
> so_txtime.c:210:3: warning: variable 'reason' is used uninitialized
> whenever switch default is taken [-Wsometimes-uninitialized]
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests/net: initialize char variable to null
https://git.kernel.org/netdev/net-next/c/af7273cc7ae0
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-11-27 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 16:53 [PATCH net-next v2] selftests/net: initialize char variable to null Ankit Khushwaha
2025-11-27 0:01 ` Willem de Bruijn
2025-11-27 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=176420340676.1898314.13893932035551539532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ankitkhushwaha.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.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).