From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: pabeni@redhat.com, edumazet@google.com, borisp@nvidia.com,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
john.haxby@oracle.com
Subject: Re: [PATCH v8 3/4] net/handshake: Add Kunit tests for the handshake consumer API
Date: Tue, 4 Apr 2023 17:24:04 -0700 [thread overview]
Message-ID: <20230404172404.335cac5c@kernel.org> (raw)
In-Reply-To: <168054757552.2138.13089316455964656033.stgit@klimt.1015granger.net>
On Mon, 03 Apr 2023 14:46:15 -0400 Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> These verify the API contracts and help exercise lifetime rules for
> consumer sockets and handshake_req structures.
Does it build with allmodconfig for you?
error: the following would cause module name conflict:
lib/kunit/kunit-test.ko
net/handshake/kunit-test.ko
next prev parent reply other threads:[~2023-04-05 0:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:45 [PATCH v8 0/4] Another crack at a handshake upcall mechanism Chuck Lever
2023-04-03 18:46 ` [PATCH v8 1/4] net/handshake: Create a NETLINK service for handling handshake requests Chuck Lever
2023-04-04 15:36 ` Chuck Lever III
2023-04-04 15:44 ` Hannes Reinecke
2023-04-05 0:00 ` Jakub Kicinski
2023-04-05 6:32 ` Hannes Reinecke
2023-04-05 14:10 ` Chuck Lever III
2023-04-05 0:23 ` Jakub Kicinski
2023-04-05 0:44 ` Chuck Lever III
[not found] ` <20230404183233.78895cf2@kernel.org>
2023-04-05 14:25 ` Chuck Lever III
2023-04-03 18:46 ` [PATCH v8 2/4] net/handshake: Add a kernel API for requesting a TLSv1.3 handshake Chuck Lever
2023-04-03 18:46 ` [PATCH v8 3/4] net/handshake: Add Kunit tests for the handshake consumer API Chuck Lever
2023-04-05 0:24 ` Jakub Kicinski [this message]
2023-04-05 0:45 ` Chuck Lever III
2023-04-03 18:46 ` [PATCH v8 4/4] SUNRPC: Recognize control messages in server-side TCP socket code Chuck Lever
2023-04-04 14:41 ` Chuck Lever
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=20230404172404.335cac5c@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=cel@kernel.org \
--cc=edumazet@google.com \
--cc=john.haxby@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--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 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.