mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Anders Roxell <anders.roxell@linaro.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 0/2] kselftest/seccomp: Convert to KTAP output
Date: Thu, 25 Jan 2024 14:15:09 -0700	[thread overview]
Message-ID: <41addcfe-f897-4394-bf40-aaef22c27fca@linuxfoundation.org> (raw)
In-Reply-To: <20240124-b4-kselftest-seccomp-benchmark-ktap-v4-0-cfd2bd2a31cf@kernel.org>

On 1/24/24 06:00, Mark Brown wrote:
> Currently the seccomp benchmark selftest produces non-standard output,
> meaning that while it makes a number of checks of the performance it
> observes this has to be parsed by humans.  This means that automated
> systems running this suite of tests are almost certainly ignoring the
> results which isn't ideal for spotting problems.  Let's rework things so
> that each check that the program does is reported as a test result to
> the framework.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Changes in v4:
> - Silence checkpatch noise.
> - Link to v3: https://lore.kernel.org/r/20240122-b4-kselftest-seccomp-benchmark-ktap-v3-0-785bff4c04fd@kernel.org
> 

Thank you Mark.

Applied to linux-kselftest fixes for the next rc

thanks,
-- Shuah


      parent reply	other threads:[~2024-01-25 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 13:00 Mark Brown
2024-01-24 13:00 ` [PATCH v4 1/2] kselftest/seccomp: Use kselftest output functions for benchmark Mark Brown
2024-01-24 13:00 ` [PATCH v4 2/2] kselftest/seccomp: Report each expectation we assert as a KTAP test Mark Brown
2024-01-25 21:15 ` Shuah Khan [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=41addcfe-f897-4394-bf40-aaef22c27fca@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=broonie@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luto@amacapital.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
all inboxes | Powered by JetHome®