From: Kees Cook <keescook@chromium.org>
To: shuah@kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, luto@amacapital.net, wad@chromium.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, Tim.Bird@sony.com
Subject: Re: [PATCH v5 0/5] kselftest: add fixture parameters
Date: Wed, 15 Apr 2020 09:17:18 -0700 [thread overview]
Message-ID: <202004150916.3A452C9@keescook> (raw)
In-Reply-To: <20200410172326.3ad05290@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Fri, Apr 10, 2020 at 05:23:26PM -0700, Jakub Kicinski wrote:
> On Tue, 17 Mar 2020 18:01:48 -0700 Jakub Kicinski wrote:
> > Hi!
> >
> > Shuah please consider applying to the kselftest tree.
> >
> > This set is an attempt to make running tests for different
> > sets of data easier. The direct motivation is the tls
> > test which we'd like to run for TLS 1.2 and TLS 1.3,
> > but currently there is no easy way to invoke the same
> > tests with different parameters.
> >
> > Tested all users of kselftest_harness.h.
>
> Hi Shuah!
>
> Were these applied anywhere? I'm happy to take them via
> the networking tree if that's easier.
Shuah, with -rc1 out the door, would now be a good time to take this
series?
Thanks!
-Kees
--
Kees Cook
prev parent reply other threads:[~2020-04-15 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 1:01 [PATCH v5 0/5] kselftest: add fixture parameters Jakub Kicinski
2020-03-18 1:01 ` [PATCH v5 1/5] kselftest: factor out list manipulation to a helper Jakub Kicinski
2020-03-18 1:01 ` [PATCH v5 2/5] kselftest: create fixture objects Jakub Kicinski
2020-03-18 1:01 ` [PATCH v5 3/5] kselftest: run tests by fixture Jakub Kicinski
2020-03-18 1:01 ` [PATCH v5 4/5] kselftest: add fixture variants Jakub Kicinski
2020-03-18 1:01 ` [PATCH v5 5/5] selftests: tls: run all tests for TLS 1.2 and TLS 1.3 Jakub Kicinski
2020-03-18 22:49 ` [PATCH v5 0/5] kselftest: add fixture parameters Kees Cook
2020-04-11 0:23 ` Jakub Kicinski
2020-04-15 16:17 ` Kees Cook [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=202004150916.3A452C9@keescook \
--to=keescook@chromium.org \
--cc=Tim.Bird@sony.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=wad@chromium.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 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).