From: Kees Cook <keescook@chromium.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
Will Drewry <wad@chromium.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Add kselftest_harness.h
Date: Tue, 2 May 2017 16:16:05 -0700 [thread overview]
Message-ID: <CAGXu5jKw_dCUELdGG4ORwrb5OOQoWueRhw6x8AZx94QkGW5QOA@mail.gmail.com> (raw)
In-Reply-To: <20170502222641.7142-1-mic@digikod.net>
On Tue, May 2, 2017 at 3:26 PM, Mickaël Salaün <mic@digikod.net> wrote:
> Hi,
>
> This second patch series make the seccomp/test_harness.h more generally
> available [1] and update the kselftest documentation with the Sphinx format. It
> also improve the Makefile of seccomp tests to take into account any
> kselftest_harness.h update.
>
> [1] https://lkml.kernel.org/r/CAGXu5j+8CVz8vL51DRYXqOY=xc3zuKFf=PTENe88XYHzFYidUQ@mail.gmail.com
>
> Regards,
>
> Mickaël Salaün (6):
> selftests: Make test_harness.h more generally available
> selftests: Cosmetic renames in kselftest_harness.h
> selftests/seccomp: Force rebuild according to dependencies
> Documentation/dev-tools: Add kselftest
For these four:
Acked-by: Kees Cook <keescook@chromium.org>
> Documentation/dev-tools: Use reStructuredText markups for kselftest
> Documentation/dev-tools: Add kselftest_harness documentation
These two have some minor nits I emailed about, but if those are
fixed, consider them Acked-by me too.
Thanks for this!
-Kees
>
> Documentation/00-INDEX | 2 -
> Documentation/dev-tools/index.rst | 1 +
> .../{kselftest.txt => dev-tools/kselftest.rst} | 134 +++++++++--
> MAINTAINERS | 1 +
> .../test_harness.h => kselftest_harness.h} | 268 +++++++++++++++------
> tools/testing/selftests/seccomp/Makefile | 2 +
> tools/testing/selftests/seccomp/seccomp_bpf.c | 2 +-
> 7 files changed, 307 insertions(+), 103 deletions(-)
> rename Documentation/{kselftest.txt => dev-tools/kselftest.rst} (52%)
> rename tools/testing/selftests/{seccomp/test_harness.h => kselftest_harness.h} (81%)
>
> --
> 2.11.0
>
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2017-05-02 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 22:26 [PATCH v2 0/6] Add kselftest_harness.h Mickaël Salaün
2017-05-02 22:26 ` [PATCH v2 1/6] selftests: Make test_harness.h more generally available Mickaël Salaün
2017-05-02 22:26 ` [PATCH v2 2/6] selftests: Cosmetic renames in kselftest_harness.h Mickaël Salaün
2017-05-02 22:26 ` [PATCH v2 3/6] selftests/seccomp: Force rebuild according to dependencies Mickaël Salaün
2017-05-02 22:26 ` [PATCH v2 4/6] Documentation/dev-tools: Add kselftest Mickaël Salaün
2017-05-02 22:26 ` [PATCH v2 5/6] Documentation/dev-tools: Use reStructuredText markups for kselftest Mickaël Salaün
2017-05-02 23:12 ` Kees Cook
2017-05-02 22:26 ` [PATCH v2 6/6] Documentation/dev-tools: Add kselftest_harness documentation Mickaël Salaün
2017-05-02 23:15 ` Kees Cook
2017-05-02 23:16 ` 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=CAGXu5jKw_dCUELdGG4ORwrb5OOQoWueRhw6x8AZx94QkGW5QOA@mail.gmail.com \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mic@digikod.net \
--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).