netdev.vger.kernel.org archive mirror
 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, edumazet@google.com,
	pabeni@redhat.com, borisp@nvidia.com, john.fastabend@gmail.com,
	maximmi@nvidia.com, tariqt@nvidia.com
Subject: Re: [PATCH net-next v2 0/6] tls: pad strparser, internal header, decrypt_ctx etc.
Date: Sat, 09 Jul 2022 02:50:15 +0000	[thread overview]
Message-ID: <165733501536.22629.3596736417274152283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220708010314.1451462-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  7 Jul 2022 18:03:08 -0700 you wrote:
> A grab bag of non-functional refactoring to make the series
> which will let us decrypt into a fresh skb smaller.
> 
> Patches in this series are not strictly required to get the
> decryption into a fresh skb going, they are more in the "things
> which had been annoying me for a while" category.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] strparser: pad sk_skb_cb to avoid straddling cachelines
    https://git.kernel.org/netdev/net-next/c/2d91ecace661
  - [net-next,v2,2/6] tls: rx: always allocate max possible aad size for decrypt
    https://git.kernel.org/netdev/net-next/c/50a07aa53161
  - [net-next,v2,3/6] tls: rx: wrap decrypt params in a struct
    https://git.kernel.org/netdev/net-next/c/b89fec54fd61
  - [net-next,v2,4/6] tls: rx: coalesce exit paths in tls_decrypt_sg()
    https://git.kernel.org/netdev/net-next/c/03957d84055e
  - [net-next,v2,5/6] tls: create an internal header
    https://git.kernel.org/netdev/net-next/c/587903142308
  - [net-next,v2,6/6] tls: rx: make tls_wait_data() return an recvmsg retcode
    https://git.kernel.org/netdev/net-next/c/35560b7f06b8

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



      parent reply	other threads:[~2022-07-09  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  1:03 [PATCH net-next v2 0/6] tls: pad strparser, internal header, decrypt_ctx etc Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 1/6] strparser: pad sk_skb_cb to avoid straddling cachelines Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 2/6] tls: rx: always allocate max possible aad size for decrypt Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 3/6] tls: rx: wrap decrypt params in a struct Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 4/6] tls: rx: coalesce exit paths in tls_decrypt_sg() Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 5/6] tls: create an internal header Jakub Kicinski
2022-07-08  1:03 ` [PATCH net-next v2 6/6] tls: rx: make tls_wait_data() return an recvmsg retcode Jakub Kicinski
2022-07-09  2:50 ` 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=165733501536.22629.3596736417274152283.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 \
    /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).