From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, borisp@nvidia.com, john.fastabend@gmail.com,
maximmi@nvidia.com, tariqt@nvidia.com, vfedorenko@novek.ru
Subject: Re: [PATCH net-next 0/4] tls: rx: follow ups to rx work
Date: Fri, 29 Jul 2022 05:00:15 +0000 [thread overview]
Message-ID: <165907081587.3346.17648225664118232297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220727031524.358216-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Jul 2022 20:15:20 -0700 you wrote:
> A selection of unrelated changes. First some selftest polishing.
> Next a change to rcvtimeo handling for locking based on an exchange
> with Eric. Follow up to Paolo's comments from yesterday. Last but
> not least a fix to a false positive warning, turns out I've been
> testing with DEBUG_NET=n this whole time.
>
> Jakub Kicinski (4):
> selftests: tls: handful of memrnd() and length checks
> tls: rx: don't consider sock_rcvtimeo() cumulative
> tls: strp: rename and multithread the workqueue
> tls: rx: fix the false positive warning
>
> [...]
Here is the summary with links:
- [net-next,1/4] selftests: tls: handful of memrnd() and length checks
https://git.kernel.org/netdev/net-next/c/86c591fb9142
- [net-next,2/4] tls: rx: don't consider sock_rcvtimeo() cumulative
https://git.kernel.org/netdev/net-next/c/70f03fc2fc14
- [net-next,3/4] tls: strp: rename and multithread the workqueue
https://git.kernel.org/netdev/net-next/c/d11ef9cc5a67
- [net-next,4/4] tls: rx: fix the false positive warning
https://git.kernel.org/netdev/net-next/c/e20691fa36c4
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:[~2022-07-29 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 3:15 [PATCH net-next 0/4] tls: rx: follow ups to rx work Jakub Kicinski
2022-07-27 3:15 ` [PATCH net-next 1/4] selftests: tls: handful of memrnd() and length checks Jakub Kicinski
2022-07-27 3:15 ` [PATCH net-next 2/4] tls: rx: don't consider sock_rcvtimeo() cumulative Jakub Kicinski
2022-07-28 13:50 ` Paolo Abeni
2022-07-28 15:42 ` Jakub Kicinski
2022-07-28 15:47 ` Eric Dumazet
2022-07-28 20:04 ` Paolo Abeni
2022-07-27 3:15 ` [PATCH net-next 3/4] tls: strp: rename and multithread the workqueue Jakub Kicinski
2022-07-27 3:15 ` [PATCH net-next 4/4] tls: rx: fix the false positive warning Jakub Kicinski
2022-07-29 5: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=165907081587.3346.17648225664118232297.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
--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.