From: Chuck Lever <cel@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: pabeni@redhat.com, edumazet@google.com, netdev@vger.kernel.org,
kernel-tls-handshake@lists.linux.dev
Subject: Re: [PATCH v9 3/3] net/handshake: Add Kunit tests for the handshake consumer API
Date: Fri, 14 Apr 2023 22:06:59 -0400 [thread overview]
Message-ID: <ZDoGw3nVG+jNWrwV@manet.1015granger.net> (raw)
In-Reply-To: <20230414183113.318ee353@kernel.org>
On Fri, Apr 14, 2023 at 06:31:13PM -0700, Jakub Kicinski wrote:
> On Thu, 13 Apr 2023 15:14:08 -0400 Chuck Lever wrote:
> > net/Kconfig | 15 +
> > net/handshake/.kunitconfig | 11 +
> > net/handshake/Makefile | 2
> > net/handshake/handshake-test.c | 523 ++++++++++++++++++++++++++++++++++++++++
> > net/handshake/netlink.c | 22 ++
> > net/handshake/request.c | 5
> > 6 files changed, 578 insertions(+)
> > create mode 100644 net/handshake/.kunitconfig
> > create mode 100644 net/handshake/handshake-test.c
>
> We're getting:
>
> net/handshake/.kunitconfig: warning: ignored by one of the .gitignore files
>
> during allmodconfig build, any idea where that's coming from?
As far as I know, all of the .kunitconfig files in the kernel tree
are marked "ignored". I'm not sure why, nor if it's a significant
problem.
next prev parent reply other threads:[~2023-04-15 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:13 [PATCH v9 0/3] Another crack at a handshake upcall mechanism Chuck Lever
2023-04-13 19:13 ` [PATCH v9 1/3] net/handshake: Create a NETLINK service for handling handshake requests Chuck Lever
2023-04-13 19:14 ` [PATCH v9 2/3] net/handshake: Add a kernel API for requesting a TLSv1.3 handshake Chuck Lever
2023-04-13 19:14 ` [PATCH v9 3/3] net/handshake: Add Kunit tests for the handshake consumer API Chuck Lever
2023-04-15 1:31 ` Jakub Kicinski
2023-04-15 2:06 ` Chuck Lever [this message]
2023-04-15 2:15 ` Jakub Kicinski
2023-04-15 3:39 ` Chuck Lever
2023-04-15 17:57 ` Chuck Lever III
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=ZDoGw3nVG+jNWrwV@manet.1015granger.net \
--to=cel@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).