All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, shuah@kernel.org,
	vfedorenko@novek.ru
Subject: Re: [PATCH net 1/2] selftests: tls: clean up uninitialized warnings
Date: Mon, 21 Jun 2021 19:20:04 +0000	[thread overview]
Message-ID: <162430320499.6988.9835964890406190142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210618202504.1435179-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri, 18 Jun 2021 13:25:03 -0700 you wrote:
> A bunch of tests uses uninitialized stack memory as random
> data to send. This is harmless but generates compiler warnings.
> Explicitly init the buffers with random data.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
>  tools/testing/selftests/net/tls.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)

Here is the summary with links:
  - [net,1/2] selftests: tls: clean up uninitialized warnings
    https://git.kernel.org/netdev/net-next/c/baa00119d69e
  - [net,2/2] selftests: tls: fix chacha+bidir tests
    https://git.kernel.org/netdev/net-next/c/291c53e4dacd

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-06-21 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 20:25 [PATCH net 1/2] selftests: tls: clean up uninitialized warnings Jakub Kicinski
2021-06-18 20:25 ` [PATCH net 2/2] selftests: tls: fix chacha+bidir tests Jakub Kicinski
2021-06-18 22:03   ` Vadim Fedorenko
2021-06-18 22:02 ` [PATCH net 1/2] selftests: tls: clean up uninitialized warnings Vadim Fedorenko
2021-06-21 19: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=162430320499.6988.9835964890406190142.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=vfedorenko@novek.ru \
    /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.