From: Chuck Lever III <chuck.lever@oracle.com>
To: "kernel-tls-handshake@lists.linux.dev"
<kernel-tls-handshake@lists.linux.dev>
Subject: pre-release of v7
Date: Thu, 9 Mar 2023 14:41:18 +0000 [thread overview]
Message-ID: <D6172FF4-D42F-4677-987E-D0B80326AD11@oracle.com> (raw)
Hi-
I'm now trying to take a step or two towards a more typical development
process for the kernel patches and ktls-utils, as we replace the old
upcall mechanism with netlink. This is in preparation for a release of
ktls-utils-0.8, once netdev is close to happy with the kernel part.
I have pushed pre-release branches of v7 so you can comment early, test
it, or send me patches /before/ I post "Another crack at a handshake
upcall mechanism" v7 on netdev@. What a concept, eh?
Kernel part: The upcall-v7 branch in
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
User space part: The netlink-v7 branch in
https://github.com/oracle/ktls-utils
The one thing I'm waiting on now is for Jakub to deal properly with
the license and copyright notices in the YAML specs and generated C
source code. As an old SunRPC hand, I feel that the code generator
needs to copy the spec's license and copyright notices verbatim to
the generated C code. Jakub is not certain this is required; his code
generator adds a license notice that is sometimes not compatible with
the spec's license.
We are planning to loop the Linux Foundation in to try to extract some
legal advice.
--
Chuck Lever
next reply other threads:[~2023-03-09 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 14:41 Chuck Lever III [this message]
2023-03-09 18:29 ` pre-release of v7 Hannes Reinecke
2023-03-09 20:20 ` Chuck Lever III
2023-03-09 20:34 ` Hannes Reinecke
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=D6172FF4-D42F-4677-987E-D0B80326AD11@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
/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).