All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <shuah@kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Jiri Slaby <jirislaby@kernel.org>
Cc: Michal Sekletar <msekleta@redhat.com>,
	linux-serial@vger.kernel.org,  linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,  Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/2] kselftest/tty: Improve integration with automated systems
Date: Wed, 06 Mar 2024 19:21:24 +0000	[thread overview]
Message-ID: <20240306-kselftest-tty-tname-v1-0-33505b31629e@kernel.org> (raw)

This cleans up the output of the tty_tstamp_update selftest to play a
bit more nicely with automated systems parsing the test output.

To do this I've also added a new helper ksft_test_result() which takes a
KSFT_ code as a report, this is something I've wanted on other occasions
but restructured things to avoid needing it.  This time I figured I'd
just add it since it keeps coming up.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      kselftest: Add mechanism for reporting a KSFT_ result code
      kselftest/tty: Report a consistent test name for the one test we run

 tools/testing/selftests/kselftest.h             | 22 ++++++++++++
 tools/testing/selftests/tty/tty_tstamp_update.c | 48 +++++++++++++++++--------
 2 files changed, 55 insertions(+), 15 deletions(-)
---
base-commit: 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478
change-id: 20240305-kselftest-tty-tname-5411444ce037

Best regards,
-- 
Mark Brown <broonie@kernel.org>


             reply	other threads:[~2024-03-06 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 19:21 Mark Brown [this message]
2024-03-06 19:21 ` [PATCH 1/2] kselftest: Add mechanism for reporting a KSFT_ result code Mark Brown
2024-03-06 19:21 ` [PATCH 2/2] kselftest/tty: Report a consistent test name for the one test we run Mark Brown
2024-03-06 22:51 ` [PATCH 0/2] kselftest/tty: Improve integration with automated systems Greg Kroah-Hartman
2024-03-26 19:49   ` Shuah Khan
2024-03-26 20:07     ` Mark Brown

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=20240306-kselftest-tty-tname-v1-0-33505b31629e@kernel.org \
    --to=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=msekleta@redhat.com \
    --cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.