From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, netdev@vger.kernel.org,
borisp@nvidia.com, john.fastabend@gmail.com,
daniel@iogearbox.net, vfedorenko@novek.ru
Subject: Re: [PATCH net-next 00/10] tls: rx: random refactoring part 1
Date: Fri, 08 Apr 2022 11:10:18 +0000 [thread overview]
Message-ID: <164941621866.19376.2276042715754218799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220408033823.965896-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Apr 2022 20:38:13 -0700 you wrote:
> TLS Rx refactoring. Part 1 of 3. A couple of features to follow.
>
> Jakub Kicinski (10):
> tls: rx: jump to a more appropriate label
> tls: rx: drop pointless else after goto
> tls: rx: don't store the record type in socket context
> tls: rx: don't store the decryption status in socket context
> tls: rx: init decrypted status in tls_read_size()
> tls: rx: use a define for tag length
> tls: rx: replace 'back' with 'offset'
> tls: rx: don't issue wake ups when data is decrypted
> tls: rx: refactor decrypt_skb_update()
> tls: hw: rx: use return value of tls_device_decrypted() to carry
> status
>
> [...]
Here is the summary with links:
- [net-next,01/10] tls: rx: jump to a more appropriate label
https://git.kernel.org/netdev/net-next/c/bfc06e1aaa13
- [net-next,02/10] tls: rx: drop pointless else after goto
https://git.kernel.org/netdev/net-next/c/d5123edd10cf
- [net-next,03/10] tls: rx: don't store the record type in socket context
https://git.kernel.org/netdev/net-next/c/c3f6bb74137c
- [net-next,04/10] tls: rx: don't store the decryption status in socket context
https://git.kernel.org/netdev/net-next/c/7dc59c33d62c
- [net-next,05/10] tls: rx: init decrypted status in tls_read_size()
https://git.kernel.org/netdev/net-next/c/863533e316b2
- [net-next,06/10] tls: rx: use a define for tag length
https://git.kernel.org/netdev/net-next/c/a8340cc02bee
- [net-next,07/10] tls: rx: replace 'back' with 'offset'
https://git.kernel.org/netdev/net-next/c/5deee41b19b3
- [net-next,08/10] tls: rx: don't issue wake ups when data is decrypted
https://git.kernel.org/netdev/net-next/c/5dbda02d322d
- [net-next,09/10] tls: rx: refactor decrypt_skb_update()
https://git.kernel.org/netdev/net-next/c/3764ae5ba661
- [net-next,10/10] tls: hw: rx: use return value of tls_device_decrypted() to carry status
https://git.kernel.org/netdev/net-next/c/71471ca32505
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-04-08 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 3:38 [PATCH net-next 00/10] tls: rx: random refactoring part 1 Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 01/10] tls: rx: jump to a more appropriate label Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 02/10] tls: rx: drop pointless else after goto Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 03/10] tls: rx: don't store the record type in socket context Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 04/10] tls: rx: don't store the decryption status " Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 05/10] tls: rx: init decrypted status in tls_read_size() Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 06/10] tls: rx: use a define for tag length Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 07/10] tls: rx: replace 'back' with 'offset' Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 08/10] tls: rx: don't issue wake ups when data is decrypted Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 09/10] tls: rx: refactor decrypt_skb_update() Jakub Kicinski
2022-04-08 3:38 ` [PATCH net-next 10/10] tls: hw: rx: use return value of tls_device_decrypted() to carry status Jakub Kicinski
2022-04-08 11:10 ` 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=164941621866.19376.2276042715754218799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).