From: David Miller <davem@davemloft.net>
To: kuba@kernel.org
Cc: keescook@chromium.org, shuah@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 net-next v6 0/5] kselftest: add fixture parameters
Date: Tue, 28 Apr 2020 13:31:04 -0700 (PDT) [thread overview]
Message-ID: <20200428.133104.2167354110776431026.davem@davemloft.net> (raw)
In-Reply-To: <20200428010351.331260-1-kuba@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Mon, 27 Apr 2020 18:03:46 -0700
> 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.
>
> Dave, would it be possible to take these via net-next?
> It seems we're failing to get Shuah's attention.
Sure, series applied, thanks Jakub.
prev parent reply other threads:[~2020-04-28 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 1:03 [PATCH net-next v6 0/5] kselftest: add fixture parameters Jakub Kicinski
2020-04-28 1:03 ` [PATCH net-next v6 1/5] kselftest: factor out list manipulation to a helper Jakub Kicinski
2020-04-28 1:03 ` [PATCH net-next v6 2/5] kselftest: create fixture objects Jakub Kicinski
2020-04-28 1:03 ` [PATCH net-next v6 3/5] kselftest: run tests by fixture Jakub Kicinski
2020-04-28 1:03 ` [PATCH net-next v6 4/5] kselftest: add fixture variants Jakub Kicinski
2020-04-28 1:03 ` [PATCH net-next v6 5/5] selftests: tls: run all tests for TLS 1.2 and TLS 1.3 Jakub Kicinski
2020-04-28 20:31 ` David Miller [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=20200428.133104.2167354110776431026.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Tim.Bird@sony.com \
--cc=keescook@chromium.org \
--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