From: patchwork-bot+netdevbpf@kernel.org
To: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sd@queasysnail.net,
shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests: tls: fix warning of uninitialized variable
Date: Wed, 10 Dec 2025 09:20:18 +0000 [thread overview]
Message-ID: <176535841802.523551.13219087665647345862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251205163242.14615-1-ankitkhushwaha.linux@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 5 Dec 2025 22:02:42 +0530 you wrote:
> In 'poll_partial_rec_async' a uninitialized char variable 'token' with
> is used for write/read instruction to synchronize between threads
> via a pipe.
>
> tls.c:2833:26: warning: variable 'token' is uninitialized
> when passed as a const pointer argument
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: tls: fix warning of uninitialized variable
https://git.kernel.org/netdev/net/c/9580f6d47dd6
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-12-10 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 16:32 [PATCH net-next v2] selftests: tls: fix warning of uninitialized variable Ankit Khushwaha
2025-12-06 10:27 ` Simon Horman
2025-12-10 9:06 ` Jakub Kicinski
2025-12-10 9:23 ` Simon Horman
2025-12-10 9:20 ` 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=176535841802.523551.13219087665647345862.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=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=sd@queasysnail.net \
--cc=shuah@kernel.org \
/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.