public inbox for kernel-tls-handshake@lists.linux.dev
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chuck Lever <cel@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	kernel-tls-handshake@lists.linux.dev
Subject: Re: [PATCH net-next v3 0/7] In-kernel support for the TLS Alert protocol
Date: Fri, 28 Jul 2023 22:40:25 +0000	[thread overview]
Message-ID: <169058402506.15090.8253785395174410667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <169047923706.5241.1181144206068116926.stgit@oracle-102.nfsv4bat.org>

Hello:

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

On Thu, 27 Jul 2023 13:34:56 -0400 you wrote:
> IMO the kernel doesn't need user space (ie, tlshd) to handle the TLS
> Alert protocol. Instead, a set of small helper functions can be used
> to handle sending and receiving TLS Alerts for in-kernel TLS
> consumers.
> 
> 
> Changes since v2:
> * Simplify header dependencies
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/7] net/tls: Move TLS protocol elements to a separate header
    https://git.kernel.org/netdev/net-next/c/6a7eccef47b2
  - [net-next,v3,2/7] net/tls: Add TLS Alert definitions
    https://git.kernel.org/netdev/net-next/c/0257427146e8
  - [net-next,v3,3/7] net/handshake: Add API for sending TLS Closure alerts
    https://git.kernel.org/netdev/net-next/c/35b1b538d422
  - [net-next,v3,4/7] SUNRPC: Send TLS Closure alerts before closing a TCP socket
    https://git.kernel.org/netdev/net-next/c/5dd5ad682cfe
  - [net-next,v3,5/7] net/handshake: Add helpers for parsing incoming TLS Alerts
    https://git.kernel.org/netdev/net-next/c/39d0e38dcced
  - [net-next,v3,6/7] SUNRPC: Use new helpers to handle TLS Alerts
    https://git.kernel.org/netdev/net-next/c/39067dda1d86
  - [net-next,v3,7/7] net/handshake: Trace events for TLS Alert helpers
    https://git.kernel.org/netdev/net-next/c/b470985c76df

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-07-28 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 17:34 [PATCH net-next v3 0/7] In-kernel support for the TLS Alert protocol Chuck Lever
2023-07-27 17:35 ` [PATCH net-next v3 1/7] net/tls: Move TLS protocol elements to a separate header Chuck Lever
2023-07-27 17:35 ` [PATCH net-next v3 2/7] net/tls: Add TLS Alert definitions Chuck Lever
2023-07-27 17:36 ` [PATCH net-next v3 3/7] net/handshake: Add API for sending TLS Closure alerts Chuck Lever
2023-07-27 17:36 ` [PATCH net-next v3 4/7] SUNRPC: Send TLS Closure alerts before closing a TCP socket Chuck Lever
2023-07-27 17:37 ` [PATCH net-next v3 5/7] net/handshake: Add helpers for parsing incoming TLS Alerts Chuck Lever
2023-07-27 17:37 ` [PATCH net-next v3 6/7] SUNRPC: Use new helpers to handle " Chuck Lever
2023-07-27 17:38 ` [PATCH net-next v3 7/7] net/handshake: Trace events for TLS Alert helpers Chuck Lever
2023-07-28 22:40 ` 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=169058402506.15090.8253785395174410667.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cel@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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