All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: kuba@kernel.org, jannh@google.com, daniel@iogearbox.net,
	borisp@nvidia.com, bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] fixes for ktls
Date: Thu, 07 Dec 2023 18:00:27 +0000	[thread overview]
Message-ID: <170197202710.7796.9621509944364172901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206232706.374377-1-john.fastabend@gmail.com>

Hello:

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

On Wed,  6 Dec 2023 15:27:04 -0800 you wrote:
> Couple fixes for TLS and BPF interactions.
> 
> John Fastabend (2):
>   net: tls, update curr on splice as well
>   bpf: sockmap, updating the sg structure should also update curr
> 
>  net/core/filter.c | 19 +++++++++++++++++++
>  net/tls/tls_sw.c  |  2 ++
>  2 files changed, 21 insertions(+)

Here is the summary with links:
  - [net,1/2] net: tls, update curr on splice as well
    https://git.kernel.org/netdev/net/c/c5a595000e26
  - [net,2/2] bpf: sockmap, updating the sg structure should also update curr
    https://git.kernel.org/netdev/net/c/bb9aefde5bba

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



      parent reply	other threads:[~2023-12-07 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 23:27 [PATCH net 0/2] fixes for ktls John Fastabend
2023-12-06 23:27 ` [PATCH net 1/2] net: tls, update curr on splice as well John Fastabend
2023-12-07 16:51   ` John Fastabend
2023-12-06 23:27 ` [PATCH net 2/2] bpf: sockmap, updating the sg structure should also update curr John Fastabend
2023-12-07 18: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=170197202710.7796.9621509944364172901.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=borisp@nvidia.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jannh@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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.